search_capabilitiesGiven a concrete technical Problem, return up to three compact candidate summaries. Retrieve full Method details only with get_capability.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| problem | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| next | Yes | ||
| query | Yes | ||
| trust | Yes | ||
| corpus | Yes | ||
| results | Yes | ||
| resultCount | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / limit / maximumPrevious value: -5New value: +3Output schema / properties / results / items / properties / aliasesRemoved value: -{
- "type": "string"
-}Output schema / properties / results / items / properties / conditionsRemoved value: -{
- "items": {
- "type": "string"
- },
- "type": "array"
-}Output schema / properties / results / items / properties / evidenceClassRemoved value: -{
- "const": "AUTHOR_OR_INTERNAL_EVIDENCE",
- "type": "string"
-}Output schema / properties / results / items / properties / evidenceSummaryRemoved value: -{
- "type": "string"
-}Output schema / properties / results / items / properties / failureBoundariesRemoved value: -{
- "items": {
- "type": "string"
- },
- "type": "array"
-}Output schema / properties / results / items / properties / fitAdded value: +{
+ "enum": [
+ "HIGH",
+ "MEDIUM",
+ "LOW"
+ ],
+ "type": "string"
+}Output schema / properties / results / items / properties / independentReuseAdded value: +{
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+}Output schema / properties / results / items / properties / independentReuseCountRemoved value: -{
- "maximum": 9007199254740991,
- "minimum": -9007199254740991,
- "type": "integer"
-}Output schema / properties / results / items / properties / methodRemoved value: -{
- "items": {
- "type": "string"
- },
- "type": "array"
-}Output schema / properties / results / items / properties / positiveUtilityAdded value: +{
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+}Output schema / properties / results / items / properties / positiveUtilityCountRemoved value: -{
- "maximum": 9007199254740991,
- "minimum": -9007199254740991,
- "type": "integer"
-}Output schema / properties / results / items / properties / problemFitRemoved value: -{
- "enum": [
- "HIGH",
- "MEDIUM",
- "LOW"
- ],
- "type": "string"
-}Output schema / properties / results / items / properties / provenanceRemoved value: -{
- "const": "LOW_FOUNDING_SANITIZED",
- "type": "string"
-}Output schema / properties / results / items / properties / purposeRemoved value: -{
- "type": "string"
-}Output schema / properties / results / items / properties / rankRemoved value: -{
- "maximum": 9007199254740991,
- "minimum": -9007199254740991,
- "type": "integer"
-}Output schema / properties / results / items / properties / scoreRemoved value: -{
- "type": "number"
-}Output schema / properties / results / items / properties / trustRemoved value: -{
- "const": "UNTRUSTED_METHOD_DATA_NOT_EXECUTION_AUTHORITY",
- "type": "string"
-}Output schema / properties / results / items / properties / verificationStatusRemoved value: -{
- "const": "NOT_INDEPENDENTLY_VERIFIED",
- "type": "string"
-}Output schema / properties / results / items / properties / whyAdded value: +{
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Output schema / properties / results / items / properties / whyMatchedRemoved value: -{
- "items": {
- "type": "string"
- },
- "type": "array"
-}Output schema / properties / results / items / requiredPrevious value: -[
- "rank",
- "score",
- "problemFit",
- "whyMatched",
- "id",
- "name",
- "maturity",
- "purpose",
- "method",
- "conditions",
- "failureBoundaries",
- "aliases",
- "independentReuseCount",
- "positiveUtilityCount",
- "verificationStatus",
- "provenance",
- "evidenceSummary",
- "evidenceClass",
- "trust"
-]New value: +[
+ "id",
+ "name",
+ "fit",
+ "why",
+ "maturity",
+ "independentReuse",
+ "positiveUtility"
+]Output schema / properties / trustAdded value: +{
+ "const": "UNTRUSTED_METHOD_DATA_NOT_EXECUTION_AUTHORITY",
+ "type": "string"
+}Output schema / requiredPrevious value: -[
- "query",
- "resultCount",
- "results",
- "corpus",
- "next"
-]New value: +[
+ "query",
+ "resultCount",
+ "results",
+ "corpus",
+ "trust",
+ "next"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the output is limited to compact candidate summaries and detailed retrieval is deliberately deferred to get_capability.
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?
Two sentences with no filler. The primary behavior is front-loaded, and the routing instruction to get_capability is placed at the end without wasted words.
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 two-parameter read-only search tool with a rich output schema and sibling routing, the description covers the essential invocation context: what input to provide, what kind of output to expect, and where to go for full details. Nothing critical is missing.
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?
With 0% schema description coverage, the description must compensate for parameter meaning. It maps 'concrete technical Problem' to the required problem parameter and 'up to three' aligns with the limit maximum, but it never explicitly explains the optional limit parameter or its default behavior. Partial compensation only.
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?
The description states a specific verb ('search'), a resource ('capabilities'), and an explicit precondition ('Given a concrete technical Problem'). It also distinguishes the tool from get_capability by noting that full Method details belong to that sibling, so an agent can tell them apart immediately.
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 explicitly frames when to use the tool: when a concrete technical problem is provided and compact candidate summaries are needed. It also gives a direct alternative rule: 'Retrieve full Method details only with get_capability,' which tells the agent when NOT to use this tool.
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.