Skip to main content
Glama

Clareo Health clinical trials

Compare clinical trials

compare_clinical_trials
Read-onlyIdempotent

Read two to five public clinical trials by NCT ID in one call, with the fields that matter side by side: status, phase, conditions, interventions, sponsor, ages, sex, healthy volunteers, enrollment, dates and site count. Use it after search_clinical_trials when a person is choosing between trials. An ID the registry does not know comes back in notFound. Registry contacts are left out. Not medical advice; do not rank trials for a person.

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": {
      "nctIds": "<nctIds>"
    },
    "name": "compare_clinical_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
nctIdsYesTwo to five ClinicalTrials.gov IDs.

Output Schema

NameRequiredDescriptionDefault
trialsYes
notFoundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, yet the description still adds real information: unknown IDs surface in a notFound result (partial success rather than wholesale failure), registry contacts are stripped from output, and the no-medical-advice boundary is stated. It stops short of covering caching, rate limits, or how a malformed-ID call fails, keeping it off the top mark.

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?

The action and cardinality are front-loaded, and the routing hint follows immediately. It is efficient overall, though the long mid-sentence field list and the two trailing policy clauses read slightly as a run-on.

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 an output schema present and rich annotations, the description need not explain return values, and it correctly avoids that. It covers the remaining agent-relevant gaps for a one-parameter comparison tool: the field set compared, the notFound path, omitted contact data, and the advice/ranking boundary.

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% and already encodes the NCT pattern plus minItems/maxItems, so the description's 'two to five ... by NCT ID' is largely restating structured data. The only semantic addition is that unknown IDs come back as notFound rather than erroring, which is marginal at the parameter level.

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?

States a specific verb (read), resource (clinical trials), cardinality (two to five), identifier type (NCT ID), and output shape (fields side by side). The enumerations of compared fields makes it unmistakable versus get_clinical_trial (single trial) and search_clinical_trials (discovery).

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use it after search_clinical_trials when a person is choosing between trials') and an explicit constraint on use ('do not rank trials for a person'). The ordering dependency on a named sibling removes nearly all ambiguity about when to pick this tool.

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