TrialBase DB

trials_search

Read-onlyIdempotent

Search trials by condition, intervention, sponsor, phase, status, country, or free text.

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": "trials_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No
`limit`	No
`phase`	No
`cursor`	No
`status`	No
`country`	No
`sponsor`	No
`registry`	No
`condition`	No
`study_type`	No
`intervention`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds nothing further — no result-set semantics, no pagination behavior, no indication of whether multiple filters AND together or how matching works.

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?

A single front-loaded sentence with no filler, which is structurally sound. The brevity tips into under-specification given the 11-parameter surface rather than trimming genuine excess.

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

Completeness2/5

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

For an 11-parameter search tool with no output schema and no parameter documentation, the description leaves the agent guessing about pagination (cursor/limit defaults), registry and study_type filtering, and result shape. It is not complete enough to call reliably without opening the schema.

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% across 11 parameters, so the description carries the full burden. It names roughly seven facets (condition, intervention, sponsor, phase, status, country, free text via q) but omits limit, cursor, registry and study_type entirely, and gives no value formats or examples for any parameter.

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 ("Search") and resource ("trials") and enumerates the facets that can be searched. The name contrast with the sibling trials_get (retrieve a single record) is inferable, but the description does not explicitly differentiate itself from it.

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

Usage Guidelines2/5

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

No guidance on when to use this search over trials_get, no mention of what happens with zero filters, no note on paging through results with cursor, and no exclusions.

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

All TrialBase DB 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?