Skip to main content
Glama

search_literature

Read-onlyIdempotent

Search publications and preprints in Europe PMC (PubMed, PMC, bioRxiv and others).

query: free text or Europe PMC syntax (e.g. 'grain size QTL 6A', 'TITLE:"pan-genome"'). gene: optional gene name or Ensembl ID; its curated synonyms and RefSeq IDs are OR-ed into the query (e.g. gene='FLC' or gene='BnaC09g12820D'). Words are matched in title and abstract; full_text=True also searches open-access full text. crop_only requires Brassica/canola/rapeseed/Camelina in title or abstract. sort: 'relevance', 'date' (newest first) or 'cited'. Returns hit count and papers with DOI/PMID, year, journal, open-access flag, citations and a short abstract.

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_literature"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneNo
sortNorelevance
limitNo
queryYes
crop_onlyNo
from_yearNo
full_textNo
open_access_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered; the description adds real behavioral context beyond that — matching happens in title and abstract, gene terms are expanded and OR-ed, and the default crop_only=true silently narrows results. It also previews the return payload (hit count, DOI/PMID, year, journal, open-access flag, citations, short abstract), which matters since there is no 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.

Conciseness5/5

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

Front-loads the one-line purpose, then uses labelled lines keyed to parameter names, so a scanning agent can jump straight to the relevant clause. Every sentence adds information — no restatement of the name or filler.

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 an 8-parameter, annotation-light, output-schema-less search tool, it covers the purpose, the matching behavior, the return shape and most parameters. The remaining gap is the undocumented limit, from_year and open_access_only parameters, which an agent must infer from names alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description must carry parameter meaning, and it does so for five of eight params, including query syntax examples ('TITLE:"pan-genome"'), gene identifier examples, and the accepted sort values ('relevance', 'date' newest first, 'cited'). limit, from_year and open_access_only are left entirely to the bare schema, which keeps this from a 5.

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 ("Search publications and preprints") and pins down the corpus as Europe PMC with the constituent sources enumerated (PubMed, PMC, bioRxiv and others). The resource is unique among the listed siblings (get_paper fetches by identifier, search_data covers other data), so an agent can route correctly without opening the 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?

Gives concrete conditional guidance: full_text=True extends matching to open-access full text, crop_only restricts to Brassica/canola/rapeseed/Camelina in title or abstract, and gene OR-s its curated synonyms and RefSeq IDs into the query. It does not name an alternative tool or state when not to use it, so it falls short of a 5.

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