The Cure Protocol

get_mission_map

Read-only

USE WHEN starting disease research or a swarm: the 15 disease domains with ontology ids (MONDO/EFO), indexed and active trial counts (active = recruiting, active or not yet recruiting), research links and a per-domain parallel work plan (this replaces list_research_diseases, which still works as an alias); pass swarm=N for a deterministic split of N agents across domains and lanes. For overall trial totals use totals.uniqueIndexedTrials / totals.uniqueActiveTrials; never sum the per-domain counts (trials in several domains would double count). Coverage gaps, not a ranking. NEXT: get_disease_dossier, then the lanes in parallel, then submit_finding.

Input Schema

Name	Required	Description	Default
`swarm`	No	Agents to assign.

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"
+}

AddedOct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Consistent with readOnlyHint=true and openWorldHint=false. Beyond the annotations it discloses semantic traps: 'active' means recruiting or not yet recruiting, coverage gaps are not a ranking, and per-domain counts overlap so totals must come from the aggregate fields — exactly the kind of behavior that prevents a wrong call.

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-loaded with the trigger and packed with useful detail, but the semicolon-chain and stacked parentheticals (alias note, active definition, totals pointer) make it a dense block rather than a scannable structure. Little is wasted, though the alias note could be shorter.

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?

An output schema exists so return-shape explanation isn't required, and the description still covers the interpretation gotchas (double counting, gaps vs ranking) plus the downstream workflow. Nothing an agent needs to call 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% and the one parameter is trivially described, so baseline is 3. The description still adds value beyond 'Agents to assign.' by explaining the effect: a deterministic split of N agents across domains and lanes, which tells the agent the output shape changes with swarm.

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?

Names the exact resource returned: 15 disease domains with MONDO/EFO ontology ids, indexed/active trial counts with an explicit definition of 'active', research links, and a per-domain parallel work plan. It also disambiguates from siblings by stating it replaces list_research_diseases and that overall totals live in totals.uniqueIndexedTrials/totals.uniqueActiveTrials.

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

Usage Guidelines5/5

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

Opens with an explicit trigger ('USE WHEN starting disease research or a swarm'), gives a parameter-level usage rule (pass swarm=N for a deterministic split), an explicit anti-pattern (never sum per-domain counts), and a NEXT chain (get_disease_dossier, then lanes in parallel, then submit_finding). Alternatives and exclusions are stated rather than inferred.

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?