Skip to main content
Glama
Augmented-Nature

Unofficial Clinical Trials MCP Server

search_by_intervention

Search clinical trials by intervention, drug, device, or treatment name. Filter by type and phase to find relevant studies.

Instructions

Search clinical trials by intervention or treatment type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
interventionYesIntervention, drug, device, or treatment name
interventionTypeNoType of intervention
phaseNoStudy phase filter
pageSizeNoNumber of results to return (default 10, max 100)
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the search intent without explaining what the tool returns, whether pagination is applied, or any side effects. This is insufficient for an agent to understand the tool's behavior.

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?

The description is a single sentence with no wasted words. It is front-loaded with the verb 'Search' and the resource. However, it could be slightly more informative without losing conciseness.

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?

Given that there is no output schema, the description should clarify what the tool returns (e.g., study IDs, summaries). It does not. Additionally, with 4 parameters and no behavioral context, the description is too minimal to fully guide an agent.

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?

The input schema has 100% coverage with descriptions for all four parameters, including enumerated types for interventionType and phase. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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?

The description clearly states the tool searches clinical trials by intervention or treatment type, using a specific verb and resource. However, it does not differentiate from sibling tools like search_by_condition or search_by_location, which also search clinical trials by other criteria.

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 guidance is provided on when to use this tool versus the many sibling search tools (e.g., search_by_condition, search_by_eligibility_criteria). The description does not mention alternatives or context that would help an agent decide.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Augmented-Nature/ClinicalTrials-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server