The Cure Protocol

find_tools

Read-only

FIND THE RIGHT TOOL for a job described in plain words, without reading the whole inventory. Returns matching tools with purpose, read or write, and the words that matched. NEXT: describe_tool for the full input schema and a worked example.

Input Schema

Name	Required	Description	Default
`q`	Yes	What you want to do, in plain words.
`limit`	No	How many tools to return.

Output Schema

Name	Required	Description	Default
`data`	No	The answer. Shape depends on the tool; describe_tool documents it.
`_meta`	No	source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "_meta": {
+      "additionalProperties": {},
+      "description": "source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "data": {
+      "description": "The answer. Shape depends on the tool; describe_tool documents it."
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 24, 2026
- addedInput schema / properties / q / maxLength
```
Added value: +500
```
AddedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds real value by disclosing what comes back ('purpose, read or write, and the words that matched'), which reveals the underlying keyword-matching mechanism and signals a ranked/annotated result rather than raw objects.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and scope, followed by a single next-step pointer. Every clause earns its place; there is no restatement of the name or filler.

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

Completeness4/5

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

A low-complexity two-parameter search tool with an output schema, a full safety annotation set, and an explicit handoff to describe_tool — the agent has what it needs to call it and to act on results. The only minor gap is whether matching is keyword-only, which limits how the agent should phrase `q`.

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

Parameters3/5

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

Schema description coverage is 100%, so both `q` and `limit` are already documented in the schema. The description reinforces that `q` is a plain-language job description but adds no syntax, phrasing advice, or guidance on choosing `limit`. Baseline 3 applies when the schema carries the parameter burden.

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

Purpose5/5

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

States a specific verb+resource ('FIND THE RIGHT TOOL') and a precise scope ('for a job described in plain words, without reading the whole inventory'). An agent can immediately distinguish this from list_capabilities (enumerate everything) and describe_tool (fetch one schema).

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?

'Without reading the whole inventory' implicitly routes the agent away from exhaustive listing tools, and 'NEXT: describe_tool' gives an explicit follow-up step once a match is found. It stops short of naming an explicit when-not or a named alternative sibling, so it is clear context rather than full routing guidance.

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

All The Cure Protocol tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?