The Cure Protocol

get_disease_drugs

Read-only

LIST DRUGS AND CLINICAL CANDIDATES studied for a disease domain, deduplicated, with stage, mechanism, targets and trial reports; filter by stage. Alphabetical, not an efficacy ranking. NEXT: search_compounds for one molecule, find_repurposing_leads for approved drugs not yet tried here.

Input Schema

Name	Required	Description
`id`	Yes	Domain id, e.g. endocrinology.
`limit`	No	Molecules to return.
`stage`	No	APPROVAL, PHASE_3, PHASE_2, PHASE_1 and others.
`ontologyId`	No	One of the domain's ontology ids.

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

Changed3 schema fields changedOct 24, 2026
- addedInput schema / properties / id / maxLength
```
Added value: +20000
```
- addedInput schema / properties / ontologyId / maxLength
```
Added value: +20000
```
- addedInput schema / properties / stage / maxLength
```
Added value: +20000
```
AddedOct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's job is the extras: it discloses deduplication, the fields carried per entry (stage, mechanism, targets, trial reports), and the non-scientific alphabetical ordering. It stops short of any cost, rate, or truncation behavior for a tool with a limit up to 200, which keeps it from a 5.

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?

One dense front-loaded sentence covering purpose, contents, and the ordering caveat, followed by a short routing clause. Every clause carries distinct information; nothing is restated from the title or schema.

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?

With annotations handling safety, 100% schema coverage handling parameters, and an output schema handling return shape, the description only needed purpose, ordering caveat, and sibling routing — all present. An agent can call this correctly with no further reading.

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 coverage is 100%, so the baseline is 3. The description adds only 'filter by stage' on top of a schema that already spells out id, limit, stage values and ontologyId — it clarifies intent but contributes no format or interaction detail the agent can't read in the schema.

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?

Opens with a specific verb+resource ('LIST DRUGS AND CLINICAL CANDIDATES studied for a disease domain') and immediately qualifies scope with deduplication and returned fields. The explicit contrast with search_compounds ('for one molecule') and find_repurposing_leads ('approved drugs not yet tried here') lets an agent separate this from the two nearest siblings without opening either schema.

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?

The 'NEXT:' clause names both alternatives and the exact condition that selects each — one molecule vs. an untried-approved-drug search. It also states the ordering caveat ('Alphabetical, not an efficacy ranking'), which prevents a plausible downstream misuse of the results.

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?