Skip to main content
Glama
Augmented-Nature

Unofficial Clinical Trials MCP Server

get_similar_studies

Find clinical trials similar to a given study using NCT ID. Filter by condition, intervention, sponsor, or phase to discover related research.

Instructions

Find clinical trials similar to a specific study by NCT ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nctIdYesNCT ID of the reference study (e.g., NCT00000419)
similarityTypeNoType of similarity to search forCONDITION
pageSizeNoNumber of results to return (default 10, max 50)
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states that it finds similar trials but does not explain what 'similar' means, whether the operation is read-only, or any side effects. This leaves significant gaps for the AI agent.

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 that is very concise and directly communicates the tool's main purpose. While it could benefit from a bit more structure, it is efficient and has no wasted words.

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?

Given the tool has 3 parameters and no output schema, the description provides a basic understanding of what the tool does. However, it does not mention what the tool returns (e.g., a list of study IDs or details), which would be helpful for completeness.

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 clear descriptions for each parameter including constraints (pattern, enum, min/max). The description adds no additional meaning beyond what the schema already provides, so it meets the baseline of 3.

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 finds clinical trials similar to a specific study by NCT ID. This is a specific verb+resource combination that distinguishes it from sibling tools like search_by_condition or get_recruiting_studies.

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 gives no explicit guidance on when to use this tool versus alternatives. It is implied that it is useful when you have an NCT ID and want similar studies, but no exclusions or comparisons to sibling tools are provided.

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