Blossom Research

Read a clinical trial record

get_trial

Read-onlyIdempotent

Retrieve full structured data for a single clinical trial by slug, including arms, interventions (compound + dose + route), eligibility criteria, sponsor, registry info, and up to 20 registry endpoint-schedule rows with measures and timing. Use after search_trials when the question is about a specific trial, or when the chat is anchored to a trial detail page. endpointSchedule rows are registry evidence, not proof of exact procedures, safety, eligibility, or waiver; endpointScheduleTotal reports when the bounded rows are incomplete.

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": {
      "slug": "<slug>"
    },
    "name": "get_trial"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, but the description adds real behavioral context beyond them: results are capped at 20 endpoint-schedule rows, endpointScheduleTotal signals truncation, and the rows are explicitly labeled registry evidence rather than proof of procedures or eligibility. It does not mention auth or rate limits, keeping it short of 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.

Conciseness4/5

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

Three front-loaded sentences with no filler: purpose first, then routing guidance, then the caveat about bounded rows. The first sentence is dense with field lists but every item aids selection, so waste is minimal.

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 an output schema and full annotations, the description covers everything an agent needs: what is returned, when to use it, and how to interpret the bounded endpointSchedule data. Return-value detail is complementary rather than duplicative.

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

Parameters2/5

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

Schema description coverage is 0% and the single 'slug' parameter has no description, format, or example. The phrase 'by slug' restates the field name, and the only implicit hint about where a slug comes from is the mention of search_trials; the description does not compensate for the coverage gap.

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 ('Retrieve full structured data for a single clinical trial by slug') and enumerates the payload (arms, interventions, eligibility, sponsor, registry info, endpoint-schedule rows), which clearly separates it from the search_* siblings.

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?

Explicitly names the preceding tool and condition: 'Use after search_trials when the question is about a specific trial, or when the chat is anchored to a trial detail page.' That is an unambiguous when-to-use rule plus the alternative path.

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

All Blossom Research tools Inspect

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

Need Help?