Skip to main content
Glama
Sign In
PubCrawl

PubCrawl

by nickjlamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_trial

Read-only

Retrieve complete details of a clinical trial by NCT ID, including eligibility criteria, study design, arms, outcomes, locations, and linked PubMed references.

Instructions

Get detailed information about a specific clinical trial from ClinicalTrials.gov. Returns eligibility criteria, study design, arms, outcomes, locations, and associated PubMed IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nctId": "<nctId>"
    },
    "name": "get_trial"
  }
}

Input Schema

NameRequiredDescriptionDefault
nctIdYesClinicalTrials.gov NCT identifier (e.g., NCT03086486)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnly, openWorld, and non-destructive behavior. The description adds context beyond that by naming the external source and detailing exactly which subsets of trial data are returned, which is especially valuable because no output schema exists.

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, information-dense sentence that front-loads the core purpose and then lists the relevant return values. Every phrase earns its place, with no filler or repetition.

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 single-parameter lookup tool with no output schema, the description covers the essential return fields and the data source. It does not explain not-found behavior or response envelope, but that is minor given the tool's simplicity and strong annotations.

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 the nctId parameter is already well documented with a pattern and example. The description does not add parameter-level meaning, but the baseline of 3 applies because the schema carries the full burden.

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 specifies the exact verb ('get'), the resource ('a specific clinical trial from ClinicalTrials.gov'), and enumerates the returned content. This makes the tool's purpose clear and distinguishes it from search_trials and other siblings.

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 clearly implies use when detailed information about a specific trial is needed, especially given a required nctId. However, it never explicitly states when not to use it or names alternatives like search_trials, leaving comparison guidance to inference.

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