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 symbol or IWGSC ID; its curated synonyms and RefSeq IDs are OR-ed into the query (e.g. gene='Lr34' also matches Yr18, Sr57, TraesCS7D02G080300). Words are matched in title and abstract; full_text=True also searches open-access full text. crop_only requires wheat/Triticum/Aegilops 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
Behavior5/5

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

Annotations only declare the read/idempotent/open-world profile, and the description goes well beyond that: it explains that gene synonyms and RefSeq IDs are OR-ed into the query with a concrete Lr34/Yr18/Sr57 example, that words match title and abstract unless full_text is set, that crop_only enforces wheat/Triticum/Aegilops in title or abstract, and what the response contains (hit count, DOI/PMID, year, journal, OA flag, citations, short abstract).

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 core sentence followed by labeled, one-line-per-parameter notes; no filler, and the return-format sentence is placed last where it belongs.

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 search tool with no output schema, the description supplies return fields and matching behavior, so an agent can call it correctly. Missing pagination/limit guidance and from_year semantics are the remaining shortfall.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does for query, gene, full_text, crop_only and sort (including valid sort values 'relevance', 'date', 'cited'). It leaves limit, from_year and open_access_only undocumented, which is a real gap given the low schema coverage.

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 in Europe PMC') and names the covered corpora (PubMed, PMC, bioRxiv), so an agent can distinguish it from get_paper or search_data 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: it shows query syntax examples and explains that full_text=True widens matching to open-access full text, which helps an agent choose settings. It never says when to prefer this over a sibling like get_paper (for fetching a known paper) or states prerequisites/exclusions, so guidance remains implicit.

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