Skip to main content
Glama

search_trials

Read-only

Search ClinicalTrials.gov registrations by condition, intervention, sponsor, phase, status or terms to find relevant trials; use returned NCT IDs to fetch citable passages.

Instructions

Search ClinicalTrials.gov registrations (give a condition, intervention or terms). Returns trial summaries; fetch nct: records for citable passages.

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": "search_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
termsNoAny other words, e.g. a sponsor
cursorNo
phasesNo
statusesNoOverall status, e.g. COMPLETED
conditionNoe.g. heart failure
has_resultsNoOnly trials with (true) or without (false) results
interventionNoe.g. dapagliflozin

Output Schema

NameRequiredDescriptionDefault
hitsYes
totalYes
next_cursorNo
source_statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With readOnlyHint and openWorldHint already declared, the annotations carry the safety and reach profile. The description adds genuinely useful context that results are summaries rather than full citable text, but says nothing about pagination behavior, result volumes, or the cursor-driven continuation that an 8-parameter search tool implies.

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?

Two short sentences with the primary action and inputs front-loaded, followed by the follow-up path. No filler or restated boilerplate.

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?

Return values need no explanation because an output schema exists, and the main search dimensions are covered. However, the cursor parameter has no schema description and is unmentioned here, leaving the agent without guidance on how to page through results in a tool that caps at 50 per call.

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 63%, and the description only echoes the three free-text entry points already described in the schema (condition, intervention, terms). It adds no meaning for phases, statuses, has_results, limit, or cursor beyond what the schema states, so it neither compensates for nor improves on the structured fields.

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?

Names a specific verb and a specific resource ('Search ClinicalTrials.gov registrations'), and gives the three primary inputs to supply. It stops short of explicitly contrasting with sibling searches like search_literature or search_drug_labels, but the registry-specific framing makes the domain clear.

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?

Tells the agent what to supply (condition, intervention or terms) and signals a scope boundary: this returns summaries, and citable passages require fetching nct: records. That is a useful use-vs-next-step routing hint, though no explicit when-not-to-use guidance or alternative-search naming is given.

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