The Cure Protocol

get_trial_landscape

Read-only

USE WHEN you need the SHAPE of a research field rather than a list of its members: phase / status / study-type mix, sponsor concentration, enrollment scale, the completed-but-unreported results gap, momentum over 30/90/365 days, and a real diff against a stored earlier snapshot. READ fieldCompleteness BEFORE QUOTING ANY DISTRIBUTION — if phase is recorded for a quarter of a registry's records, the phase mix describes that quarter, not the field. evidenceGap reports the reporting failure per registry and deliberately refuses to publish a combined figure when the registries' results flags are not comparable. NEXT: search_world_trials to inspect the trials behind a bucket, get_trial_coverage to check how much of the population is duplicate registrations.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free-text condition/intervention query, e.g. "type 1 diabetes islet". Tokens are ANDed.
`phase`	No	Comma-separated phases, e.g. "1,2". Phase is missing for much of the corpus.
`topic`	No	Cure Protocol topic id (get_trial_stats lists them).
`status`	No	Recruitment status, or "active" for recruiting + active + not_yet_recruiting.
`country`	No	Recruiting/site country.
`sponsor`	No	Free-text sponsor name match.
`registry`	No	clinicaltrials_gov \| isrctn. OMIT for full-index scope — restricting to one registry makes the answer single-registry evidence.
`condition`	No	Exact registry condition term. Prefer q unless you know the exact string.
`studyType`	No	interventional \| observational \| expanded_access \| other.
`intervention`	No	Free-text intervention match — the way to separate MODALITIES within one disease.
`startedAfter`	No	ISO date — study start on/after.
`updatedSince`	No	ISO date — only records updated on/after this date.
`crossRegistry`	No	true = only trials registered in more than one registry.
`maxEnrollment`	No	Maximum normalized enrollment.
`minEnrollment`	No	Minimum normalized enrollment.
`startedBefore`	No	ISO date — study start on/before.
`completionAfter`	No	ISO date — completion on/after.
`completionBefore`	No	ISO date — completion on/before.
`resultsAvailable`	No	Restrict to trials with/without posted results.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only cover readOnly/openWorld, but the description discloses deeper quirks: it warns to READ fieldCompleteness before quoting a distribution, and notes evidenceGap 'deliberately refuses to publish a combined figure when the registries' results flags are not comparable'. This is real behavioral context an agent cannot get from annotations.

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 USE WHEN clause and organized around the value proposition, caveats, and next steps. Dense but each clause earns its place; the capitalized internal field names are slightly awkward but functional.

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 no output schema, the description carries the burden of describing returns, and it does so credibly (mix figures, evidenceGap, fieldCompleteness, momentum over 30/90/365 days, snapshot diff). It stops short of enumerating the actual response structure, so not a full 5.

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% with 19 self-documented parameters, so the baseline is 3. The description reinforces a few semantics (fieldCompleteness caveat, registry scoping) but adds no syntax or format detail beyond what the schema already documents.

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 and an explicit contrast: 'the SHAPE of a research field rather than a list of its members', then enumerates the shape dimensions (phase/status/study-type mix, sponsor concentration, enrollment scale, results gap, momentum, snapshot diff). This clearly separates it from list-oriented siblings like search_world_trials.

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 'USE WHEN you need the SHAPE...' and closes with routing guidance: 'NEXT: search_world_trials to inspect the trials behind a bucket, get_trial_coverage to check how much of the population is duplicate registrations.' Explicit when-to-use plus named alternatives.

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?