Skip to main content
Glama

Cochrane systematic reviews of health interventions, found

health_clinical_evidence_cochrane
Read-only

Cochrane systematic reviews of health interventions, found through PubMed (journal Cochrane Database Syst Rev): PMID, title, publication date and DOI for a search term. Citation records only (no abstract, no full text). Up to 10 per call. Related tools on this server, for a different need: health_clinical_pharmacogenetics when you need CPIC pharmacogenetics guidelines for a gene symbol; health_clinical_trials_gov when you need ClinicalTrials.gov study search: NCT ID, title, status. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "health_clinical_evidence_cochrane"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch words, letters, digits, spaces and hyphens, 2 to 100 characters
maxNoHow many reviews, 1 to 10 (default 5)

Output Schema

NameRequiredDescriptionDefault
queryNo
totalNo
sourceNo
reviewsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-annotation context: results are citation records only with no abstract or full text, capped at 10 per call, and priced at $0.002 per successful call via x402 with failed calls uncharged. Those cost and content-limit disclosures are the main value added beyond annotations, but return shape and ordering are left to the output schema.

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?

Front-loads the resource and retrieved fields, then the citation-only limit and per-call cap, then sibling routing and pricing. Dense and purposeful, though the payment-network enumeration ('USDC on Base, Solana and 10 more networks') is longer than the agent strictly needs to select or invoke the tool.

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?

For a two-parameter read-only search with a full input schema and an output schema, the description covers scope, result kind, result cap, and cost, which is enough to call correctly. Minor residual gaps — no guidance on query syntax or result ordering — are low impact given the schemas.

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 description coverage is 100%, so both parameters are already documented, including the 2–100 character search string and the 1–10 count range. The description only restates the 'up to 10 per call' cap and the notion of a search term, adding no format, syntax, or query-operator detail beyond the schema. Baseline 3 applies.

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 pairing — Cochrane systematic reviews found through PubMed, limited to the Cochrane Database Syst Rev journal — and enumerates the returned fields (PMID, title, publication date, DOI). It also explicitly names sibling tools it is not, so an agent can distinguish it without inspecting 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?

Gives clear routing conditions for two siblings ('health_clinical_pharmacogenetics when you need CPIC pharmacogenetics guidelines for a gene symbol', 'health_clinical_trials_gov when you need ClinicalTrials.gov study search') and states the scope limit of citation records only, no abstract/full text. It stops short of stating when not to use it, e.g. for non-Cochrane literature searches or general PubMed queries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources