Skip to main content
Glama
yeyuan98

BioMCP

by yeyuan98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

trial_search

Read-only

Search clinical trials by condition, intervention, or keyword to find relevant studies. Filter results by phase, status, or intervention type.

Instructions

Search clinical trials by condition, intervention, or keyword

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results
phaseNoFilter by phase (Phase 1, Phase 2, etc.). The matched phase(s) are echoed per row in the "phase" array (e.g. ["PHASE1","PHASE2"]) so the filter is verifiable from each result
queryYesCondition, intervention, or keyword to search for
statusNoFilter by status (Recruiting, Completed, etc.)
page_tokenNoPage token from previous response for pagination
intervention_typeNoFilter by intervention type (Drug, Device, etc.); verifiable per row via the "interventions" strings ("TYPE: name")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0-alpha.10
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv1.6.0-alpha.7
    • changedInput schema / properties / intervention_type / description
      Previous value: -"Filter by intervention type (Drug, Device, etc.)"New value: +"Filter by intervention type (Drug, Device, etc.); verifiable per row via the \"interventions\" strings (\"TYPE: name\")"
    • changedInput schema / properties / phase / description
      Previous value: -"Filter by phase (Phase 1, Phase 2, etc.)"New value: +"Filter by phase (Phase 1, Phase 2, etc.). The matched phase(s) are echoed per row in the \"phase\" array (e.g. [\"PHASE1\",\"PHASE2\"]) so the filter is verifiable from each result"
  3. Changed1 schema field changedv1.6.0-alpha.1
    • addedInput schema / properties / query / minLength
      Added value: +1
  4. First observedv0.1.8

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond what the schema states—no mention of result ordering, pagination behavior via page_token, or the size/nature of the underlying registry.

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?

A single efficient sentence with no waste, and the core action is front-loaded. It is arguably clipped to the point of under-specification, but as a conciseness measure it is tight.

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

Completeness2/5

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

For a six-parameter search tool in a crowded sibling set with no output schema, the description is too thin: it omits pagination behavior, relative positioning versus the other trial tools, and any sense of result shape or scale. An agent can invoke it but has little help invoking it correctly among alternatives.

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 six parameters including phase, status, intervention_type, and page_token are documented in the schema itself, some with verifiability notes. The description restates the query facets but adds no semantics beyond the schema, making the baseline 3 correct.

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?

States a specific verb and resource ("Search clinical trials") plus the searchable facets, so the basic operation is clear. However, with six sibling trial-related tools (trial_get, drug_trials, gene_trials, disease_trials, variant_trials, discover), the description gives no clue how this differs from them.

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?

No when-to-use guidance, no exclusions, and no named alternatives. An agent cannot tell from the description whether to use trial_search, trial_get, or the entity-scoped *_trials siblings for a given request.

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

Deploy Server

Other Tools