Lists every available operation and its parameters as a JSON schema, optionally filtered by app, so you can discover supported actions before invoking them.
List every available operation with its parameters (JSON schema).
| Name | Required | Description | Default |
|---|---|---|---|
| app | No | Only operations of this app (device, ui, gmail, calendar, drive, ...). |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the result includes each operation's parameters as a JSON schema, but it does not discuss safety, side effects, rate limits, or pagination. For a read-only catalog tool this is adequate, though not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence with zero waste; it directly states what the tool returns.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple meta-listing tool with one optional filter and no output schema, the description says enough: it identifies the catalog output and the inclusion of parameter schemas. It could be slightly more complete by noting that the app filter is optional, but that is already covered by the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the single optional `app` parameter is already fully documented in the schema. The description does not add any parameter semantics beyond that baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: list every available operation with its parameters and JSON schema. This clearly distinguishes the tool from the many sibling operation tools, which perform actions rather than catalog them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies discovery usage but gives no explicit when-to-use guidance, no when-not-to-use conditions, and no alternatives. An agent must infer that this is a catalog/discovery tool rather than being told.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.