Skip to main content
Glama
Sign In

Tlacuilo

by io.github.mastercobeos
OverviewDiscussionsAdmin

clinical_trials_search

clinical_trials_search
Read-only

Clinical trial search on ClinicalTrials.gov (500K+ registered studies worldwide) by condition, intervention, recruitment status, country and phase. Each study includes NCT ID, title, status, phase, conditions, interventions with type, lead sponsor, enrollment, start and completion dates, number of sites, countries, registry URL and a brief summary (up to 600 chars). Returns the total match count and up to 50 studies per call. Price: $0.005 USDC per call (x402).

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoStudies to return, 1-50 (default 10)
phaseNoComma-separated phases: 0 (early phase 1), 1, 2, 3, 4, na (optional)
statusNoComma-separated overall status: RECRUITING, NOT_YET_RECRUITING, ACTIVE_NOT_RECRUITING, COMPLETED, ENROLLING_BY_INVITATION, SUSPENDED, TERMINATED, WITHDRAWN, UNKNOWN (optional)
countryNoCountry or city of study locations (optional)
conditionNoDisease or condition, e.g. type 2 diabetes
interventionNoDrug, device or procedure name (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds meaningful context beyond readOnlyHint: an explicit per-call price ($0.005 USDC via x402), a hard result cap (50 per call), and the fact that a total match count is returned alongside results. It does not disclose result ordering or whether pagination beyond 50 is possible, which keeps it from a 5.

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?

Two dense sentences: scope and filters first, then return payload and limits/pricing. The field enumeration is long but each item tells the agent what it gets back, and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating returned fields (NCT ID, status, phase, sponsor, enrollment, dates, sites, countries, summary length) and stating the result cap and cost. For a read-only 6-parameter search tool, an agent has enough to call and interpret it correctly.

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%, so all six parameters are already documented in the schema, including comma-separated encodings for phase and status. The description only restates the filter names, adding no new syntax or matching-behavior detail beyond the schema, so the baseline 3 applies.

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?

Names a specific verb and resource (clinical trial search on ClinicalTrials.gov), states the corpus size (500K+ studies), and enumerates the five filter dimensions. No sibling covers clinical trials, so an agent can route to it unambiguously.

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?

Usage is implied by the search framing and the listed filter dimensions, but there is no explicit when-to-use guidance, no note on whether filters are ANDed or how free-text condition/intervention matching behaves, and no mention of alternatives. The agent must infer query semantics.

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

All Tlacuilo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources