Skip to main content
Glama

clinical_trials

Read-onlyIdempotent

Search clinical trials, or get one by NCT id with eligibility criteria and sites. (cost: 1 credit)

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": "clinical_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNonumber 1-50
nctIdNostring
statusNoRECRUITING|COMPLETED|ACTIVE_NOT_RECRUITING|...
locationNostring
conditionNostring
interventionNostring

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing the cost (1 credit) and by noting that the single-record mode returns eligibility criteria and sites, which hints at shape of results. It does not describe pagination, result caps, or what search mode returns.

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?

A single front-loaded sentence covering both modes plus cost, with no filler. An agent gets the operation and the two entry points in one read.

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 six-parameter, zero-required, fully documented read-only search tool with no output schema, the description covers the operations and the cost. The remaining gap is how the filter parameters combine in search mode and what search mode returns, which is a minor omission at this complexity.

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%, so every parameter is documented in the schema itself, establishing a baseline of 3. The description adds no syntax, formatting, or combination semantics beyond naming the NCT-id path; the schema's own descriptions are minimal (e.g. "string", "number 1-50"), so the description could have compensated but does not.

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") and covers a second mode ("get one by NCT id with eligibility criteria and sites"). It is clear what the tool does, but it does not distinguish itself from adjacent literature/scholarly siblings such as pubmed_search or papers_search in the same toolset.

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 two operating modes are implied by the description — keyword/field search versus lookup by NCT id — so an agent can infer which parameters to reach for. There is no explicit when-to-use guidance, no statement that search mode and NCT-id mode should not be mixed, and no routing advice against the biomedical search siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources