The Cure Protocol

search_compounds

Read-only

FIND A DRUG OR MOLECULE in ChEMBL by name or id: max clinical phase, approval year, synonyms and mechanisms of action with references. NEXT: get_gene for the target, search_literature for trials and outcomes.

Input Schema

Name	Required	Description
`q`	No	Name or synonym. q or chemblId is required.
`limit`	No	Molecules to return.
`chemblId`	No	Exact ChEMBL id.

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

Changed2 schema fields changedOct 24, 2026
- addedInput schema / properties / chemblId / maxLength
```
Added value: +20000
```
- addedInput schema / properties / q / maxLength
```
Added value: +500
```
AddedOct 20, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-lookup profile is covered. The description adds the returned field set (phase, approval year, synonyms, MoA, references) but says nothing about ambiguous name resolution, rate limits, or empty results — extra behavioral context that would earn a higher score.

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 resource, then the follow-up routing. No filler; every clause carries information.

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?

With an output schema, annotations, and 100% parameter coverage, the description supplies the essential purpose, source, and next steps. It could be more complete about multi-match behavior and result caps, but nothing critical for correct invocation is missing.

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 q, chemblId, and limit are fully documented in the schema. The description only restates 'by name or id,' which maps to the schema but adds no syntax, precedence, or limit guidance; baseline 3 is appropriate.

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 (FIND), resource (drug or molecule), and source (ChEMBL), plus the key lookup keys (name or id). It also enumerates the returned attributes, so an agent can distinguish it from get_disease_drugs or find_repurposing_leads without opening schemas.

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?

The 'NEXT:' clause explicitly routes follow-up work to get_gene and search_literature, giving clear context for downstream usage. It stops short of naming the direct alternative for compound lookup itself (e.g., find_repurposing_leads) or stating when not to use it, so it is clear but not fully exclusionary.

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?