Skip to main content
Glama

Clareo Health clinical trials

List a trial's sites

get_trial_sites
Read-onlyIdempotent

List the sites (facility, city, state, country) where one public clinical trial runs, optionally only those in a city or state. Paged: when hasMore is true, call again with page set to nextPage. Registry contacts are not returned; the trial's page on clareohealth.com links to them. Send an NCT ID and a place only, never personal health details.

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

Input Schema

NameRequiredDescriptionDefault
cityNoKeep sites in this city.
pageNo
limitNoSites per page.
nctIdYesClinicalTrials.gov ID.
stateNoKeep sites in this state or region.

Output Schema

NameRequiredDescriptionDefault
urlYes
pageYes
nctIdYes
sitesYes
totalYesSites that match the city and state filters.
hasMoreYes
nextPageYes
totalSitesYesAll sites the registry lists for the trial.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (which already declare readOnly, idempotent, open-world, non-destructive), the description discloses the pagination contract, an important content exclusion ('registry contacts are not returned') with a redirect to where they are available, and a privacy constraint on what data to send. This is meaningful behavioral context an agent could not infer from the structured fields.

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, front-loaded with purpose, then the paging loop, then exclusions and the input constraint. Every sentence carries a distinct, actionable point with no restatement of 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?

An output schema exists, so return values need not be spelled out, and the description still surfaces the one output field that drives agent behavior (hasMore/nextPage). For a single-required-parameter filtered list tool, nothing an agent needs to call it correctly is missing.

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 coverage is 80%, so city/state/limit/nctId are already documented; the baseline would be 3. The description adds value by tying page to the nextPage/hasMore loop, which the schema does not express, and by framing city/state as narrowing filters rather than free text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('List the sites ... where one public clinical trial runs') and even enumerates the returned fields (facility, city, state, country). It is clearly distinct from trial-detail or eligibility siblings, but it never explicitly contrasts itself with them, so it stops short of a 5.

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?

It explains that city/state are optional narrowing filters and gives a concrete operational rule ('when hasMore is true, call again with page set to nextPage'). It does not name a sibling or state when a different tool would be preferable, so there are no explicit exclusions.

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