Zovo Trial Finder

Get clinical trial details

get_trial_details

Read-onlyIdempotent

Use this when someone gives a ClinicalTrials.gov ID (NCT number) and wants that study's eligibility criteria, open sites, contacts and status from the live record, with a PDF and a CSV of open sites. Add a city to sort sites by distance. Does not give medical advice or check whether a person qualifies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nct_id": "<nct_id>"
    },
    "name": "get_trial_details"
  }
}

Input Schema

Name	Required	Description
`city`	No	City to measure distance from, e.g. Chicago. Cities with 15,000+ people are recognized; use the nearest larger city otherwise.
`state`	No	U.S. state name or two-letter code for the city, e.g. IL. Leave empty outside the United States.
`nct_id`	Yes	ClinicalTrials.gov ID, e.g. NCT05727904.
`country`	No	Country name or two-letter code, e.g. United States or US.

Output Schema

Name	Required	Description	Default
`notes`	Yes
`sites`	Yes
`trial`	Yes
`source`	Yes
`downloads`	Yes
`disclaimer`	Yes
`sites_shown`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that: the record is pulled live from ClinicalTrials.gov (openWorld in practice), the call produces side artifacts (a PDF and a CSV of open sites), and the optional city parameter changes output ordering. It does not discuss latency, rate limits, or what happens when the NCT ID is unknown.

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?

Three short sentences, front-loaded with the activation condition and the payload, then the optional modifier, then the scope exclusions. No redundant restatement of the name or title.

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?

An output schema exists and annotations are rich, so the description only needs to frame the call. It does that well by naming the artifacts and data sections returned, though it does not say what an agent should expect on an invalid or retired NCT ID.

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 description coverage is 100%, so baseline would be 3. The description adds meaning the schema does not: the city parameter is for sorting sites by distance, not just a location filter. The state and country parameters' role in that distance calculation is left to the schema text.

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 and resource (fetch a ClinicalTrials.gov study record by NCT number) and enumerates exactly what comes back: eligibility criteria, open sites, contacts, status, plus a PDF and CSV of open sites. The trigger condition (user supplies an NCT ID) makes it clearly distinguishable from the sibling find_recruiting_trials, which is for discovery rather than lookup.

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?

"Use this when someone gives a ClinicalTrials.gov ID" gives a concrete activation condition, "Add a city to sort sites by distance" gives optional-use guidance, and the closing sentence sets two explicit exclusions (no medical advice, no eligibility checking). It does not name find_recruiting_trials as the alternative for users who have no ID yet, so routing between siblings is only implied.

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

All Zovo Trial Finder 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?