The Cure Protocol

search_literature

Read-only

SEARCH BIOMEDICAL LITERATURE (Europe PMC) with PMID, PMCID, DOI and open-access flags. Filter by disease domain, year, reviews; sort by relevance, citations or recency; page with cursor. NEXT: submit_evidence with a PMID, or resolve_identifiers.

Input Schema

Name	Required	Description
`q`	No	Search text. q or disease is required.
`sort`	No	relevance, cited or recent.
`limit`	No	Results per page.
`since`	No	Earliest publication year.
`cursor`	No	nextCursor from the previous page.
`disease`	No	Domain id, e.g. endocrinology.
`reviews`	No	Reviews only.
`fromDate`	No	Earliest first-publication date, YYYY-MM-DD.
`preprints`	No	true for preprints only, false to exclude them.
`openAccess`	No	Open-access only.

Output Schema

Name	Required	Description	Default
`data`	No	The answer. Shape depends on the tool; describe_tool documents it.
`_meta`	No	source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "_meta": {
+      "additionalProperties": {},
+      "description": "source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "data": {
+      "description": "The answer. Shape depends on the tool; describe_tool documents it."
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedOct 24, 2026
- addedInput schema / properties / cursor / maxLength
```
Added value: +20000
```
- addedInput schema / properties / disease / maxLength
```
Added value: +20000
```
- addedInput schema / properties / fromDate / maxLength
```
Added value: +20000
```
- addedInput schema / properties / q / maxLength
```
Added value: +500
```
- addedInput schema / properties / sort / maxLength
```
Added value: +20000
```

Changed2 schema fields changedOct 20, 2026

addedInput schema / properties / fromDate

Added value: +{
+  "description": "Earliest first-publication date, YYYY-MM-DD.",
+  "type": "string"
+}

addedInput schema / properties / preprints

Added value: +{
+  "description": "true for preprints only, false to exclude them.",
+  "type": "boolean"
+}

AddedOct 20, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds useful context that results are paged with a cursor and carry identifiers and OA flags. It omits result caps, whether limit is enforced server-side, and how broad 'open world' querying behaves, which matters for a literature search.

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

Conciseness5/5

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

Front-loaded with the action in caps, then filters, sort, and paging in a single compact clause, followed by a one-line next step. No filler and every phrase carries operational information.

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 an output schema present, return values need no narration, and all 10 parameters are schema-documented. The remaining gap is query-construction guidance (how q is interpreted, whether disease and q are ANDed), which an agent must guess.

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?

Schema coverage is 100%, so the baseline is 3; the description maps filter dimensions (disease domain, year, reviews) and sort options to their parameters, adding light reinforcement. It does not clarify free-text q syntax or how q combines with disease, which is the one genuinely ambiguous part of the schema.

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?

A specific verb plus resource (SEARCH BIOMEDICAL LITERATURE) with the upstream source named (Europe PMC) and the identifier types returned (PMID, PMCID, DOI, open-access flags). This clearly separates it from siblings like search_cure_evidence, search_datasets, and search_world_trials.

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?

The 'NEXT: submit_evidence with a PMID, or resolve_identifiers' clause gives a concrete downstream workflow, which tells an agent what this tool feeds into. It does not, however, state when to prefer it over the other search_* siblings or what it excludes, so guidance stops short of full alternative routing.

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

All The Cure Protocol 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?