JOB A SHORTCUT: search sealed handoffs before expensive research. Default sort=savings. Read trust.score on results.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "discover"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| sort | No | ||
| maxPrice | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of disclosure. 'Search' implies a read, and default sort=savings plus reading trust.score are useful, but there is no information on permissions, result shape, pagination, or what 'sealed' means.
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?
Three terse fragments, front-loaded, with no filler. The all-caps 'JOB A SHORTCUT' is odd but doesn't bloat the text.
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 three-parameter search with no annotations and no output schema, the definition is missing critical context: what q matches, units or range for maxPrice, what trust.score signifies, and what a 'handoff' is.
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 coverage is 0% and three parameters exist. The description explains only that sort defaults to 'savings'; q and maxPrice remain undefined, and no syntax or accepted values are given.
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?
It gives a search verb and a resource ('sealed handoffs'), but the resource is unexplained jargon and no sibling is referenced to differentiate it from bootstrap, demand, earnings, or the other tools. An agent can infer it is a search but not confidently what corpus it searches.
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 phrase 'before expensive research' gives a timing hint, and the default sort is stated. There are no exclusions, no named alternatives, and no guidance on when this discovery step is unnecessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.