Skip to main content
Glama

Clareo Health clinical trials

Get a trial's eligibility

get_trial_eligibility
Read-onlyIdempotent

Read who can take part in one public clinical trial: the registry's inclusion and exclusion criteria split into lists, plus age limits, sex and whether healthy volunteers are accepted. The wording is the registry's own, unedited and not explained; explain it to the person yourself and do not tell them whether they qualify. If the registry text has no inclusion and exclusion headings, unstructured is true and only criteriaText is filled. Send an NCT ID only. Not medical advice.

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

Input Schema

NameRequiredDescriptionDefault
nctIdYesClinicalTrials.gov ID.

Output Schema

NameRequiredDescriptionDefault
sexNo
urlYes
nctIdYes
maxAgeNo
minAgeNo
exclusionYes
inclusionYes
criteriaTextNoThe registry's full eligibility text.
unstructuredYes
healthyVolunteersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, and the description adds genuine context beyond them: the text is the registry's verbatim wording, the unstructured/criteriaText-only fallback, and the prohibition on rendering a qualification verdict. What it does not address is failure behavior for an unknown or withdrawn NCT ID.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payload and the unstructured fallback are front-loaded, but the middle sentences mix scope, formatting caveats, and conduct instructions in one dense block, and 'unedited and not explained' partly restates itself. The trailing 'Not medical advice' is short and safety-relevant, so it earns its place.

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?

For a single-parameter read tool with annotations and an output schema, the description covers scope, the degenerate unstructured case, and the safety constraint on what the agent may say. An agent has everything needed to call it correctly and interpret the payload.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one fully described parameter the baseline is 3, but 'Send an NCT ID only' adds real meaning: no name, title or URL lookup is accepted, so the agent must resolve an identifier elsewhere first. The regex constraint itself lives in the schema, not the description.

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 ('Read who can take part in one public clinical trial') and enumerates the returned content (inclusion/exclusion lists, age limits, sex, healthy-volunteer acceptance), which implicitly scopes it away from the broader get_clinical_trial. It never names a sibling to contrast with, so it stops short of full differentiation.

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 gives response-level guidance ('explain it to the person yourself and do not tell them whether they qualify') and an input constraint ('Send an NCT ID only'), which usefully implies the caller must already have resolved an ID. It does not say when to prefer this over get_clinical_trial or that search_clinical_trials is how to obtain the NCT ID.

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