Skip to main content
Glama

plainyogurt21-clintrials-mcp

by ai.smithery
OverviewDiscussionsAdmin

search_trials_by_nct_ids

Retrieve specific clinical trials by NCT ID(s).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoSpecific fields to return
nct_idsYesNCT IDs to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • 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
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers almost nothing beyond the operation name. It doesn't explain what happens if NCT IDs are invalid, whether results are returned in the same order as input, rate limits, or how the 'fields' parameter filters the response.

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?

Extremely concise at six words. The single sentence is front-loaded with the verb and wastes no space. However, given the absence of annotations and the presence of similar sibling tools, the description is arguably too terse to be fully effective.

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 two-parameter tool with flat schema and no output schema, the description covers the basic intent but leaves significant gaps. Without annotations, it should explain error handling, batch behavior, or at minimum clarify the relationship to get_trial_details_batched. Adequate but incomplete.

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 coverage is 100%, establishing a baseline of 3. The description implicitly references the 'nct_ids' parameter by mentioning 'NCT ID(s)', but adds no syntax details, examples, or explanation of the 'fields' parameter's purpose beyond what the schema already states.

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?

The description provides a specific verb ('Retrieve'), resource ('clinical trials'), and scope ('by NCT ID(s)'), clearly distinguishing it from siblings like search_trials_by_condition. However, it fails to differentiate from get_trial_details and get_trial_details_batched, leaving ambiguity about which NCT ID lookup tool to use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this tool versus alternatives (particularly get_trial_details or get_trial_details_batched). No mention of prerequisites, batch size limits, or when to prefer the 'fields' parameter over retrieving full records.

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 toolsInspect
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