Skip to main content
Glama

Starfile

Find clinical trials

find_trials
Read-onlyIdempotent

Find clinical studies registered on ClinicalTrials.gov by condition, sponsor or intervention, optionally by status (e.g. RECRUITING), phase (1-4), U.S. state or country. Returns status, phase, sponsor, dates, enrolment and the registry link. Pass nct_id for one study. Registry facts only, no advice about joining.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 25).
phaseNo1, 2, 3 or 4.
stateNoU.S. state as a two-letter code (NY) or full name (New York).
nct_idNoOne study by its NCT number, e.g. NCT01234567.
statusNoRECRUITING, NOT_YET_RECRUITING, ACTIVE_NOT_RECRUITING, COMPLETED, TERMINATED, ...
countryNoCountry with a study site, e.g. "United States".
sponsorNoSponsor organisation, e.g. a drug company or university.
conditionNoDisease or condition, e.g. "glioblastoma".
interventionNoDrug, device or procedure name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile needs no restating. The description adds genuinely new context beyond them: it discloses what is returned (status, phase, sponsor, dates, enrolment, registry link) and sets a scope boundary with "Registry facts only, no advice about joining," which is important for a health-domain tool.

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 filters, then return values, then the scope caveat. Every sentence carries distinct information and nothing repeats the schema verbatim.

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 nine-parameter, output-schema-less search tool, the description covers purpose, filterable fields, the single-record shortcut, return contents, and the advisory boundary. Nothing an agent needs in order to select and 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 100%, so a baseline of 3 applies, but the description adds real meaning: it groups parameters into search keys versus optional filters and clarifies that nct_id selects a single study, implying it supersedes the filter set. That is a behavioral nuance the schema alone does not convey.

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 (find clinical studies) with the exact registry (ClinicalTrials.gov) and the dimensions you can search by (condition, sponsor, intervention). It even lists the returned fields, so an agent knows the payload shape without opening the schema, and no sibling tool overlaps this domain.

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?

Gives clear usage context: optional status/phase/location filters for list queries and "Pass nct_id for one study" for a single-record lookup, which tells the agent how to switch modes. It stops short of naming explicit alternatives or when-not conditions, but none of the sibling tools are plausible substitutes for trial search.

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