Skip to main content
Glama
lzinga

US Government Open Data MCP

by lzinga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

clinical_trials_detail

Read-onlyIdempotent

Retrieve complete clinical trial details by NCT ID, including protocol, eligibility, arms, design, locations, and contacts. Optionally request only specific sections to reduce response size.

Instructions

Get full details for a specific clinical trial by NCT ID. Returns protocol, eligibility, arms/interventions, design, locations, contacts, and oversight info. Use the fields param to request only specific sections (reduces response size).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoPipe-separated fields to return: 'NCTId|BriefTitle|EligibilityModule'. Omit for full study.
nct_idYesClinicalTrials.gov NCT ID: 'NCT06000000'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2026.4.11
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Pipe-separated fields to return: 'NCTId|BriefTitle|EligibilityModule'. Omit for full study.",
+  "type": "string"
+}
    • changedInput schema / properties / nct_id / description
      Previous value: -"ClinicalTrials.gov ID: 'NCT06000000'"New value: +"ClinicalTrials.gov NCT ID: 'NCT06000000'"
  2. First observedv2026.3.9

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds valuable behavioral context beyond the annotations: it states that omitting fields returns the full study and that using fields reduces response size, which tells the agent about the request/response trade-off. It does not repeat annotation facts, but it does disclose the filtering behavior.

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 sentences with zero fluff. The first sentence states the purpose, the second lists what data is returned, and the third gives a practical optimization tip. The most important information is front-loaded and every sentence earns its place.

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?

For a read-only detail tool with only two parameters and no output schema, the description gives a clear picture of what to expect: it names the data sections returned and explains the fields parameter's effect on response size. It does not describe error behavior or output structure, but those are less critical given the annotations and simple parameter set. Overall it is adequately complete for correct invocation.

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%: both nct_id and fields have clear descriptions in the input schema. The description adds only a minor rationale for the fields parameter ('reduces response size'), which is helpful but doesn't materially expand on the schema's own documentation. Baseline 3 is appropriate because the schema carries the semantic load.

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 opens with a specific verb and resource: 'Get full details for a specific clinical trial by NCT ID.' It then enumerates the returned sections (protocol, eligibility, arms/interventions, design, locations, contacts, oversight), which makes the tool's scope clear and differentiates it from sibling search/stats tools. This is a precise, self-contained purpose statement.

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 implies this tool is for retrieving full details when an NCT ID is already known ('by NCT ID'), and gives guidance on using the fields parameter to reduce response size. However, it never explicitly tells the agent when to choose this tool over siblings like clinical_trials_search or clinical_trials_stats, nor mentions any exclusions. Usage is implied rather than directly contrasted with alternatives.

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

Deploy Server

Other Tools