Skip to main content
Glama

Search ClinicalTrials.gov studies by condition or drug

clinical_trials
Read-only

Clinical trials from ClinicalTrials.gov matching words, optionally by status and phase: NCT id, title, status, phases, conditions, sponsor, start and completion dates, enrolment, number of locations and the study link. Information only, not medical advice. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "clinical_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCondition, drug or words
limitNo1 to 20 (default 10)
phaseNoEARLY_PHASE1, PHASE1, PHASE2, PHASE3, PHASE4 or NA (optional)
statusNoRECRUITING, COMPLETED, TERMINATED … (optional)

Output Schema

NameRequiredDescriptionDefault
queryNo
sourceNo
studiesNo
checkedAtNo
disclaimerNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), and the description adds real value on top: it discloses pricing ($0.002 per successful call), the payment rail (x402 via USDC on Base/Solana and other networks), and the important detail that failed calls are not charged. It omits pagination and rate-limit behavior, which keeps it short of a 5.

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?

The return-field list and the pricing/disclaimer note are compressed into two sentences with no filler, and the core action is stated first. The long enumeration of returned fields is dense but readable and earns its place as a scope signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return values, yet it spends most of its length enumerating returned fields instead of usage or cost-saving guidance. For a read-only search tool with full schema coverage the essential information is present, but the agent still lacks guidance on when this tool is the right choice.

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 description coverage is 100%, so every parameter is already documented in the input schema; the description only echoes that status and phase are optional filters. It adds no syntax, default, or enum detail beyond the schema, which is the correct baseline-3 behaviour.

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 names a concrete resource (ClinicalTrials.gov clinical trials) and the matching dimension (words, with optional status and phase filters), so the agent knows exactly what domain this covers. It does not explicitly differentiate itself from any sibling, but the subject matter is distinctive enough that confusion is unlikely; the 'Search ... by condition or drug' framing in the title carries the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, nor any prerequisite or exclusion guidance beyond the 'Information only, not medical advice' disclaimer, which is a legal note rather than routing guidance. An agent gets no help deciding between this and other research tools.

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