Skip to main content
Glama

Find recruiting clinical trials

find_clinical_trials
Read-onlyIdempotent

Lists clinical trials recruiting now for a cancer type, from ClinicalTrials.gov, optionally near a city, state or country and filtered by a biomarker, drug or treatment keyword and by phase. Returns up to 8 trials with NCT number, phase, sponsor, the sites closest to the requested place, a registry link, a link to the full search, and a link to an OpenCancer expert who can build a trial shortlist for a specific case. Listing a trial is not an eligibility decision; only the trial team can confirm eligibility

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": {
      "condition": "<condition>"
    },
    "name": "find_clinical_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
phaseNoOptional trial phase.
keywordNoOptional biomarker, drug, or treatment, e.g. "KRAS G12C" or "CAR-T".
locationNoOptional city, state, or country, e.g. "Boston" or "Germany" (city level, not a street address).
conditionYesCancer type or condition, e.g. "pancreatic cancer".

Output Schema

NameRequiredDescriptionDefault
totalYes
trialsYes
search_urlYes
expert_help_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional city, state, or country, e.g. \"Boston\" or \"Germany\". Never a street address."New value: +"Optional city, state, or country, e.g. \"Boston\" or \"Germany\" (city level, not a street address)."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real value beyond them: a cap of 8 results, the exact return contents, and the important scope caveat that 'listing a trial is not an eligibility decision'. Rate limits or refresh behavior are not disclosed, keeping it below 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?

It is front-loaded with the core action and scope, then the filters, then return contents, then the eligibility disclaimer — a logical order with no filler. The enumeration of return fields is slightly long, but each item is informative and the whole thing remains two sentences.

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 search tool with an output schema, the description still covers the essentials: source registry, result cap, filter dimensions, and the eligibility limitation that an agent must not over-interpret. Nothing needed to call it correctly or set user expectations is missing.

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 all four parameters (condition, location, keyword, phase) are already documented in the schema with examples and length limits. The description restates their roles in prose ('near a city, state or country', 'a biomarker, drug or treatment keyword and by phase') but adds no syntax or format detail beyond that, matching the baseline of 3 when the schema does the heavy lifting.

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?

The description names a specific verb and resource ('Lists clinical trials recruiting now for a cancer type, from ClinicalTrials.gov') plus the scope of the result set. It is clearly distinguishable from siblings like get_trial_details and ask_opencancer, which operate on a single trial or a conversational expert rather than a filtered search.

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?

It states when to use it — searching by cancer type, optionally narrowed by location, biomarker/drug keyword, or phase — and adds an escalation cue by advertising a link to an OpenCancer expert who can build a shortlist. It stops short of explicitly naming the sibling tool to call for those follow-ups, so it is clear context rather than full when/when-not guidance.

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