Retrieve detailed clinical trial information with a single NCT ID. Select sections for eligibility, locations, outcomes, or core data to get targeted answers.
Get detailed trial information by NCT ID
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| nct_id | Yes | NCT ID (e.g., "NCT01234567") | |
| sections | No | Sections to include |
Changes observed during successful MCP inspections.
v0.1.8Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and variability. The description adds 'detailed trial information' but does not elaborate on response structure, pagination, or potential errors. With annotations providing the core behavioral disclosure, the description offers minimal extra value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, immediate, and wastes no words. However, it could be slightly expanded to include more context without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given there is no output schema, the description could explain what 'detailed information' entails (e.g., sections, fields returned). The description is minimal and leaves the agent to infer the response structure from the 'sections' parameter. This is adequate but not comprehensive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not provide any additional meaning beyond the input schema. While the schema covers 67% of parameters with descriptions, the 'limit' parameter lacks a schema description and the tool description does not compensate. No parameter details are elaborated.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get', the resource 'trial information', and the required identifier 'by NCT ID'. It effectively distinguishes this tool from sibling tools like 'trial_search' which would be used for searching without a known ID.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when an NCT ID is known, but does not explicitly state when to use this tool versus alternatives like 'trial_search' or other get tools. There is no mention of prerequisites or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.