caplets 0.12.7 → 0.14.0

package/README.md

@@ -68,6 +68,18 @@ Connect Caplets to any MCP client:
 Ask your agent to use Caplets. It will see a compact capability list first, then inspect
 only the backend it needs.
 
+You can also invoke configured Caplets directly from the CLI for agent-friendly scripts and smoke tests:
+
+```sh
+caplets get-caplet context7
+caplets list-tools context7
+caplets get-tool context7.resolve-library-id
+caplets call-tool context7.resolve-library-id --args '{"libraryName":"react"}'
+caplets call-tool context7.resolve-library-id --args '{"libraryName":"react"}' --field result.id --format json
+```
+
+Direct CLI operation commands print Markdown summaries by default. Add `--format plain` for plain text or `--format json` for machine-readable JSON (`md` is accepted as an alias for `markdown`). If a downstream tool returns `isError: true`, Caplets still exits with status code 1.
+
 ## Agent Plugins
 
 Use Caplets as a normal MCP server everywhere, or install a native agent integration when
@@ -610,7 +622,10 @@ shell snippets.
       "description": "Fetch status for one service.",
       "inputSchema": {
         "type": "object",
-        "properties": { "service": { "type": "string" }, "verbose": { "type": "boolean" } },
+        "properties": {
+          "service": { "type": "string" },
+          "verbose": { "type": "boolean" }
+        },
         "required": ["service"]
       },
       "query": { "verbose": "$input.verbose" }
@@ -693,7 +708,7 @@ an existing destination file.
 
 Use `capletSets` to expose another Caplets collection as nested Caplets. Each child Caplet appears
 as one downstream tool and supports the full Caplets operation set: `get_caplet`, `check_backend`,
-`check_mcp_server`, `list_tools`, `search_tools`, `get_tool`, and `call_tool`.
+`list_tools`, `search_tools`, `get_tool`, and `call_tool`.
 
 ```json
 {
@@ -891,7 +906,6 @@ Available operations:
 
 - `get_caplet`: return the configured capability card without starting the downstream server.
 - `check_backend`: verify the selected backend, whether MCP, OpenAPI, GraphQL, HTTP, CLI, or nested Caplets.
-- `check_mcp_server`: start or connect to an MCP server and verify its tool list.
 - `list_tools`: return compact downstream tool metadata.
 - `search_tools`: search downstream tool names and descriptions within this Caplet.
 - `get_tool`: return full metadata for one exact downstream tool.
@@ -900,6 +914,26 @@ Available operations:
 Requests are strict: operation-specific extra fields are rejected, and `call_tool` requires
 `arguments` to be a JSON object.
 
+Discovery operations (`get_caplet`, `check_backend`, `list_tools`, `search_tools`, and
+`get_tool`) return wrapper-generated results whose `structuredContent.caplets` field
+identifies the Caplet with `id`, plus backend, operation, status, and elapsed time when
+available. Discovery result objects and compact tool entries also use `id` for the
+configured Caplet identity. Compact `list_tools` and `search_tools` entries may include
+input/output schema hashes; treat those
+hashes as reuse hints for a schema you have already inspected, not as a replacement for
+`get_tool` when arguments, output, or semantics are unclear.
+
+Direct `call_tool` preserves the downstream tool result shape instead of wrapping it in
+`structuredContent.result`. When the result can carry MCP metadata, Caplets adds
+`_meta.caplets` with the same call context and status. It may also include artifact metadata
+for paths mentioned by downstream content, such as screenshots, snapshots, logs, downloads,
+or other saved files. Artifact `displayPath` values are either absolute local paths or
+relative to the downstream MCP server process, not necessarily relative to the current
+project or Caplets process.
+
+For first use, the explicit progressive-discovery path is still safest: choose a Caplet,
+`search_tools` or `list_tools`, inspect uncertain tools with `get_tool`, then `call_tool`.
+
 ## Development
 
 ```sh