plainyogurt21-clintrials-mcp

get_trial_details

Get comprehensive details for a single clinical trial by NCT ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	No	Specific fields to return
`nct_id`	Yes	NCT ID of the trial to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedMar 12, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / fields / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / fields / default
```
Removed value: -null
```
addedInput schema / properties / fields / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / fields / type
```
Added value: +"array"
```

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

First observedJan 31, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it states 'comprehensive details' (hinting at data scope), it fails to mention error handling (e.g., invalid NCT ID), rate limits, authentication requirements, or whether this is a cached vs. live lookup. For a data retrieval tool with no safety annotations, this is insufficient behavioral context.

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, front-loaded sentence with zero redundancy. Every word earns its place: 'Get' (action), 'comprehensive details' (scope), 'single clinical trial' (resource), 'by NCT ID' (key parameter).

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?

For a simple lookup tool with two parameters and no output schema, the description adequately covers the basic contract. However, it misses the opportunity to explain the relationship between the optional 'fields' parameter and the sibling 'get_available_fields' tool, or to describe error conditions (e.g., trial not found).

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?

With 100% schema description coverage, the schema already fully documents both 'nct_id' and 'fields'. The description adds minimal semantic value beyond the schema, merely reinforcing that the lookup is 'by NCT ID'. It does not explain valid NCT ID formats or suggest using 'get_available_fields' to populate the 'fields' parameter.

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 provides a specific verb ('Get comprehensive details'), identifies the resource ('single clinical trial'), and specifies the lookup mechanism ('by NCT ID'). The word 'single' effectively distinguishes this tool from its sibling 'get_trial_details_batched' and differentiates it from the various 'search' tools that return lists.

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?

While the description implies usage through the word 'single' (suggesting it's for individual lookups rather than batch operations), it lacks explicit guidance on when to prefer this over 'get_trial_details_batched' or the search tools. It does not mention prerequisites like NCT ID format or when searching might be better than direct lookup.

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

All plainyogurt21-clintrials-mcp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?