plainyogurt21-clintrials-mcp

search_trials_by_intervention

Search clinical trials by intervention/treatment.

Input Schema

TableJSON Schema

Name	Required	Description
`fields`	No	Specific fields to return
`max_studies`	No	Maximum number of studies to return
`interventions`	Yes	Interventions/treatments to search for

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedMar 12, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / fields / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / fields / default
```
Removed value: -null
```
addedInput schema / properties / fields / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / fields / type
```
Added value: +"array"
```
changedInput schema / properties / max_studies / type
```
Previous value: -"integer"New value: +"number"
```

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

First observedJan 31, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether this is a read-only operation, what data source is queried, how intervention matching works (exact vs. fuzzy), or what happens when no results are found.

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 description is extremely brief (6 words) and front-loaded with the action. However, given the tool's domain complexity and lack of supporting annotations, this brevity constitutes underspecification rather than efficient conciseness—it leaves critical contextual gaps that sentences should have addressed.

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?

With no output schema, no annotations, and three parameters in a domain with multiple similar search tools, the description is insufficient. It omits expected context such as result set limits (beyond the parameter default), authentication requirements, or the relationship to other search tools on this server.

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?

The input schema has 100% description coverage, establishing a baseline of 3. The description 'Search clinical trials by intervention/treatment' aligns with the 'interventions' parameter but adds no additional semantic context, examples, or syntax guidance beyond what the schema already provides.

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?

The description provides a clear verb ('Search'), resource ('clinical trials'), and scope ('by intervention/treatment'). However, it does not explicitly differentiate from sibling tools like 'search_trials_by_condition' or 'search_trials_combined', which could create uncertainty about which search tool to use.

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 is provided on when to use this tool versus the nine other search-related siblings (e.g., 'search_trials_combined' or 'search_trials_by_condition'). There are no prerequisites, exclusions, or workflow recommendations mentioned.

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

All plainyogurt21-clintrials-mcp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?