Skip to main content
Glama

EasyCanDo

Report a missed search

report_miss

Tell EasyCanDo’s owner that search found no tool a step needed, so the catalog and search can improve. Call it only after the user agrees to send it. It sends what you give here: the search (up to 200 characters), what the step needed, and, if you want, a tool you expected and a note. Nothing else from the conversation. Reports are kept for 90 days. Up to 5 an hour.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "need": "<need>"
    },
    "name": "report_miss"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the step needed, in a sentence: “turn scanned receipts into a spreadsheet”.
noteNoAnything else the owner should know, such as what search showed instead.
queryYesThe search that missed, as you sent it to search_tools.
expectedNoA tool you expected the catalog to have, by name or link, if any.

Output Schema

NameRequiredDescriptionDefault
noteYesWhat happened, to tell the user.
sentYestrue when the report reached the site’s owner.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond the annotations: exactly which fields leave the conversation ('Nothing else from the conversation'), a 90-day retention window, and a rate limit of 5 per hour. The annotations declare openWorldHint and non-read-only behavior but say nothing about data egress, retention, or throttling, so the description is carrying real weight here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose in the first clause and the consent rule in the second, then groups payload facts and operational limits together. It slightly pads by restating the 200-character limit already in the schema, but no sentence is wasted overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a small 4-parameter write tool: purpose, consent condition, data scope, retention, and rate limit are all present, and an output schema exists so return values need no explanation. Nothing an agent needs in order to fire this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by characterizing the whole payload as the complete set of data transmitted and by clarifying that the 'expected tool' and note fields are optional, which the schema conveys only weakly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete verb-and-resource: telling EasyCanDo's owner that a search returned nothing for a step, so the catalog can improve. That framing is clearly distinct from search_tools/find_chains, which do the searching; the description never explicitly contrasts them, but the reporting intent is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a hard prerequisite — 'Call it only after the user agrees to send it' — which is exactly the kind of consent gate an agent needs before a write-ish action. It stops short of naming alternatives (e.g. 'if a tool is simply misfiled, use get_tool/search_tools again'), so the routing is clear in one direction only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources