Skip to main content
Glama

Clareo Health clinical trials

Get a clinical trial

get_clinical_trial
Read-onlyIdempotent

Read one public clinical trial by its NCT ID (for example NCT01234567): summary, status, phase, eligibility text, every site and links. Use it after search_clinical_trials, or when a person already has an NCT ID. Registry contacts are left out; the trial's page on clareohealth.com carries them. Not medical advice.

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": {
      "nctId": "<nctId>"
    },
    "name": "get_clinical_trial"
  }
}

Input Schema

NameRequiredDescriptionDefault
nctIdYesClinicalTrials.gov ID: NCT and 8 digits.

Output Schema

NameRequiredDescriptionDefault
trialYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 real context beyond that: registry contacts are deliberately excluded and are available on the trial's clareohealth.com page, plus a 'Not medical advice' caveat — a data-omission disclosure that prevents the agent from assuming the record is complete.

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 sentences, tightly ordered: what it does and returns, when to call it, then the caveats. Nothing is repeated and the identifying purpose is front-loaded.

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?

For a one-parameter read tool with a full annotation set and an output schema, the description covers purpose, invocation condition, scope of returned data, and an explicit data-exclusion caveat. There is no behavioral aspect an agent would need that is left undisclosed.

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% for the single nctId parameter, including the pattern and a description of the NCT + 8 digit format. The description's example (NCT01234567) is consistent with but redundant to the schema, so the baseline 3 applies.

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 ('Read one public clinical trial by its NCT ID') and enumerates exactly what is returned: summary, status, phase, eligibility text, every site and links. It also names the sibling search_clinical_trials, so an agent can distinguish a single-record fetch from a search without inspecting 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 Guidelines4/5

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

'Use it after search_clinical_trials, or when a person already has an NCT ID' gives a clear triggering condition and a named predecessor. It does not address when the agent should prefer the narrower siblings get_trial_eligibility or get_trial_sites, even though this tool also returns eligibility text and every site.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources