Skip to main content
Glama

FoxAPIs data sources

ClinicalTrials.gov search

clinicaltrials_search
Read-onlyIdempotent

Search registered clinical trials by condition, intervention, sponsor, status or phase; returns trials with status and dates. Costs 5 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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

Input Schema

NameRequiredDescriptionDefault
phaseNo
queryNo
statusNoRECRUITING
sponsorNo
conditionNoFor example: "asthma"
max_resultsNoFor example: 3
interventionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the description rightly spends its words elsewhere: a concrete cost model (5 credits per call, no charge when no data is returned) and an auth prerequisite (FoxAPIs key). That is real value beyond structured fields. It stops short of disclosing the schema's default status=RECRUITING filter, which silently narrows results, and says nothing about result caps or pagination.

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?

Three compact sentences with the capability stated first, followed by cost and access requirements. Every sentence carries information; the parenthetical '(free to start)' is the only mild filler. No repetition or hedging.

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?

For a 7-parameter, low-coverage, no-output-schema tool, the description covers purpose, cost and auth but leaves out material gaps: the RECRUITING default that shapes every unfiltered call, the query/condition/intervention distinction, and result-set limits. It is adequate to invoke the tool, not adequate to invoke it well.

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 only 29% across 7 parameters, so the description must carry meaning, and it partly does by naming the five searchable facets that map to parameters. But it adds no semantics beyond the property names: it never explains how query differs from condition or intervention, what status values are legal, or what max_results does. Net effect is a modest improvement over the bare schema.

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 (Search) and a specific resource (registered clinical trials, ClinicalTrials.gov), enumerates the searchable facets (condition, intervention, sponsor, status, phase) and says what comes back (trials with status and dates). The resource is clearly distinct from sibling lookups like pubmed_search or academic_paper, so an agent can route without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this when it wants trial data. There is no explicit when-not or named alternative, and no guidance on choosing between the overlapping facets (query vs condition vs intervention) which is the real selection ambiguity here. The credit-cost note hints at caution but is not guidance about when to prefer another tool.

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