mymedi-ai-mcp-server

Clinical trials search (ClinicalTrials.gov)

trials_search

Read-only

Search active clinical trials by condition, ICD-10 code, or intervention to retrieve NCT ID, phase, enrollment, and eligibility details from ClinicalTrials.gov.

Instructions

Search active clinical trials by condition, ICD-10 code, or intervention. Returns trial details including NCT ID, phase, enrollment, and eligibility. Source: ClinicalTrials.gov.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trials_search"
  }
}

Input Schema

Name	Required	Description
`code`	No	ICD-10 code (auto-mapped to condition)
`limit`	No	Max results (default 10, max 50)
`status`	No	Trial status filter (default: RECRUITING)
`condition`	No	Medical condition to search for
`intervention`	No	Drug or intervention name

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.7.9Nov 2, 2026
- addedInput schema / properties / code / maxLength
```
Added value: +200
```
- addedInput schema / properties / condition / maxLength
```
Added value: +200
```
- addedInput schema / properties / intervention / maxLength
```
Added value: +200
```
- addedInput schema / properties / limit / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
Addedv1.2.1Apr 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety and externality profile is covered. The description contributes the external data source and the shape of returned trial records, but says nothing about result limits, pagination, or what happens when no selector is supplied; the 'active' wording also conflicts mildly with the COMPLETED status option.

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?

Three short sentences with the capability and selectors front-loaded, followed by return contents and provenance. Every sentence carries distinct information and nothing is repeated from the schema verbatim.

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

Completeness4/5

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

With no output schema, the sentence enumerating NCT ID, phase, enrollment, and eligibility usefully compensates and lets an agent judge result usefulness. Minor gap: all five parameters are optional, and the description never clarifies the behavior or error when none of condition/code/intervention is provided.

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 the schema already documents all five parameters, including ICD-10 auto-mapping and the 50-result cap. The description restates three of the five selectors but adds no syntax, format, or precedence guidance (e.g., what happens if both code and condition are given), so baseline 3 applies.

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 three selector inputs and the source registry, so it is clearly distinguishable from the drug/code siblings. The one flaw is the framing as 'active clinical trials' when the schema's status enum includes COMPLETED and NOT_YET_RECRUITING, so the stated scope slightly undersells what the tool retrieves.

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?

Naming condition, ICD-10 code, and intervention implies how to drive the tool, and the title ties it to ClinicalTrials.gov. But there is no explicit when-to-use guidance, no statement about needing at least one selector, and no routing to or away from any sibling tool.

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