Skip to main content
Glama
Augmented-Nature

Unofficial Clinical Trials MCP Server

search_by_sponsor

Find clinical trials by sponsor or organization name. Optionally filter by sponsor type and page size.

Instructions

Search clinical trials by sponsor or organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sponsorYesSponsor name or organization (e.g., "Pfizer", "National Cancer Institute")
sponsorTypeNoType of sponsor
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 carries full burden. It only states 'Search clinical trials by sponsor or organization' with no disclosure of behavioral traits such as pagination, result format, or side effects. This is insufficient for an agent to understand behavior beyond basic purpose.

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?

The description is a single sentence that is concise and front-loaded. Every word contributes to the core purpose. No unnecessary information.

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 the lack of output schema and annotations, the description should provide more context about results, return structure, or limitations. It does not explain what the search returns or how to interpret results. For a tool with 3 parameters, this is incomplete.

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%, with each parameter having a description. The tool description does not add meaning beyond the schema. For baseline, score 3 is appropriate; the description merely restates the purpose without enhancing parameter understanding.

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 clearly states the tool's purpose: 'Search clinical trials by sponsor or organization'. It uses a specific verb ('search') and resource ('clinical trials'), and the 'by sponsor' qualifier distinguishes it from sibling tools like search_by_condition or search_by_location.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It implies usage through the description of filtering by sponsor, but lacks explicit conditions or exclusions. For a search tool with many siblings, this is a minor gap.

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