Skip to main content
Glama

search_medical

Evidence-graded MEDICAL literature search (PubMed + Europe PMC). Unlike search_all (generic, ranks high-cited reviews/guidelines above trials), this filters by research type via PubMed Publication-Type tags and re-ranks by the evidence pyramid (meta-analysis / systematic review > RCT > cohort > ...), so the actual clinical trials surface first. Open-access full text is pulled from Europe PMC by PMID. query should be English keyword/boolean text (PubMed maps it); do natural-language/multilingual understanding upstream. Returns hits with pmid/doi/study_type/evidence_level/citations/abstract and, when open-access, fulltext.

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": {
      "query": "<query>"
    },
    "name": "search_medical"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
year_fromNo
max_resultsNo
study_typesNorct,meta-analysis,systematic-review
fetch_fulltextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses data sources, the evidence-pyramid re-ranking behavior, that full text comes from Europe PMC by PMID, and the returned fields including evidence_level. It omits cost/latency implications of fetch_fulltext=true and any rate-limit or pagination behavior.

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?

Dense and front-loaded: purpose and sibling contrast come first, then ranking rationale, then input/output behavior. Every sentence adds information, though the long compound sentences make it slightly harder to scan than a bulleted structure.

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?

No output schema exists, and the description compensates by listing return fields (pmid/doi/study_type/evidence_level/citations/abstract/fulltext). Remaining gap is the undocumented year_from and max_results parameters and no note on result-set limits.

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 0%, so the description must compensate. It explains `query` well (English keyword/boolean, PubMed mapping) and implicitly covers study_types (PubMed Publication-Type tags) and fetch_fulltext (open-access pull), but says nothing about year_from or max_results semantics and gives no accepted values or format for study_types.

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 ('Evidence-graded MEDICAL literature search (PubMed + Europe PMC)') and explicitly contrasts itself with search_all, including the differing ranking logic and why trials surface first. An agent can distinguish this from search_all or search_papers without opening any schema.

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?

Names the alternative (search_all) and the condition that selects this tool (medical/clinical evidence queries where research type matters), and tells the caller to do natural-language understanding upstream. It stops short of stating when NOT to use it, e.g. non-medical topics or when only author/institution lookup is needed.

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.