Skip to main content
Glama

SolvingHealth federal health data

search_trials

Search ClinicalTrials.gov (API v2) for registered studies. Use for "what is recruiting for knee OA", evidence landscape questions, or checking whether a claimed trial exists.

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
limitNoMax results, 1-50
statusNoOverall status, e.g. RECRUITING, COMPLETED
locationNoWhere the study runs: a state, city or country, e.g. "Colorado"
conditionNoCondition, e.g. "knee osteoarthritis"
interventionNoIntervention or drug/device name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. Calling it a search of a public registry implies read-only, non-destructive behavior, but it says nothing about rate limits, authentication, pagination, default result counts, or what a match looks like. Useful but incomplete for an unannotated 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?

Two sentences, front-loaded with the source and resource, followed by the concrete decision scenarios. Nothing is padding and nothing essential is buried.

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

Completeness4/5

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

For a five-parameter, all-optional search with no output schema and no annotations, the description covers what is queried and why an agent would call it. It stops short of describing result shape or how multiple filters combine, which would matter for an agent composing a precise query.

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% and every parameter already has an example in the schema, so the description can only add marginal value. The sample query phrasings implicitly show how condition and status combine in practice, but no parameter is explained beyond what the schema already states.

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 resource ("Search ClinicalTrials.gov ... for registered studies") and identifies the underlying API version, so the agent knows exactly what corpus is queried. It does not explicitly contrast itself with siblings like search_adverse_events or search_drug_labels, but the resource name is distinct enough that confusion is unlikely.

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?

Provides three concrete use cases — recruitment questions ("what is recruiting for knee OA"), evidence-landscape questions, and existence checks for a claimed trial. These give real context for selection, though it never states when NOT to use it or points to a preferred alternative for adjacent questions.

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.