Skip to main content
Glama
Sign In

divux

by si.divux
OverviewDiscussionsAdmin

Trials: recruiting clinical trials for a condition

check_trials
Read-only

Returns clinical trials recruiting now for a condition, from ClinicalTrials.gov: title, phase, sponsor, who can join (age, sex, healthy volunteers), the nearest recruiting site and its distance, and the study page. A city and state or ZIP code searches within a radius. An age keeps only trials that accept that age. Applies to questions about which clinical trials are recruiting for a condition. Not medical advice. A medicine label, a recall report and a pharmacy price are outside this result.

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": {
      "condition": "<condition>"
    },
    "name": "check_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNo
limitNo
placeNoA city and state or ZIP code, e.g. 'Boston, MA' or '02108'.
conditionYesCondition, e.g. 'type 1 diabetes', 'early-stage triple negative breast cancer'
interventionNoA drug or treatment to narrow to, e.g. 'pembrolizumab'
radius_milesNoDefault 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / lat
      Removed value: -{
-  "maximum": 90,
-  "minimum": -90,
-  "type": "number"
-}
    • removedInput schema / properties / lon
      Removed value: -{
-  "maximum": 180,
-  "minimum": -180,
-  "type": "number"
-}
    • changedInput schema / properties / place / description
      Previous value: -"Name of the place, e.g. 'Boston, MA'. Used to find the place when lat and lon are left out"New value: +"A city and state or ZIP code, e.g. 'Boston, MA' or '02108'."
  2. Changed1 schema field changed
    • changedInput schema / properties / place / description
      Previous value: -"Name of the place, for the answer"New value: +"Name of the place, e.g. 'Boston, MA'. Used to find the place when lat and lon are left out"
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the safety bar is low; the description still adds useful behavior: results are limited to currently recruiting trials, the nearest site and distance are computed, and the output is framed as not medical advice. It omits call-volume or rate details, which is a minor gap.

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?

Purpose and source are front-loaded, followed by return fields, filter behavior, and exclusions in a tight sequence with no filler. The sentence 'A city and state or ZIP code searches within a radius' is slightly awkward in construction but still earns its place.

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?

With no output schema, the description does the necessary work of listing what comes back (title, phase, sponsor, eligibility, nearest site and distance, study page). The one meaningful omission is the limit parameter's purpose and default, leaving a gap for a 6-parameter tool.

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?

Beyond the 67%-covered schema, the description explains that place is combined with radius_miles to search within a radius and that age filters to trials accepting that age — both non-obvious interactions. It says nothing about limit, which neither the schema nor description documents.

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 and resource ('Returns clinical trials recruiting now for a condition') plus the data source (ClinicalTrials.gov) and enumerates the fields returned. It also explicitly excludes what siblings like check_medicine, check_recalls and compare_prices cover, so the agent can route correctly without opening schemas.

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

Usage Guidelines4/5

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

'Applies to questions about which clinical trials are recruiting for a condition' gives a clear triggering context, and the closing sentence rules out medicine labels, recalls and pharmacy prices. It stops short of naming the sibling tools to redirect to, but the boundary is unambiguous.

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

All divux 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