Skip to main content
Glama
wos-mcp-bridge

wos-mcp-bridge

Search Literature

search_literature
Read-onlyIdempotent

Retrieve life-sciences articles and abstracts from Europe PMC by query, with cursor-based paging and DOI/PMCID deduplication.

Instructions

Search one Europe PMC page for life-sciences articles and abstracts.

Use Europe PMC syntax, e.g. (canine OR dog) AND pulmonary AND FIRST_PDATE:[2020 TO 2026]. max_chars bounds total abstract text for this page. Results are deduplicated by DOI/PMCID. Supply next_cursor explicitly for another page. No OpenAlex requests or XML downloads.

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
limitNoMaximum records in this explicit page.
queryYesEurope PMC life-sciences query syntax; this is distinct from WoS syntax.
cursorNoOpaque Europe PMC next_cursor from the previous page; * starts a search.*
max_charsNoMaximum returned text characters; metadata is additional.

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
cursorYes
resultsYes
max_charsYes
retrievalYes
limitationsYes
next_cursorYes
returned_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, idempotent, non-destructive behavior, and the description adds material context: one-page execution, DOI/PMCID deduplication, explicit next_cursor pagination, and max_chars bounding abstract text. It does not cover rate limits or authentication, but with annotations and an output schema the behavioral picture is reasonably complete.

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 core action and constrained to five short sentences; each sentence adds scope, syntax, pagination, or exclusion information. The compact prose is appropriate for an agent-facing search 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?

Given four parameters, 100% schema descriptions, rich annotations, and an output schema, the description covers the operational essentials: source, query syntax, page size, pagination, and text cap. The main omission is alternative-tool routing, which keeps it from being fully complete.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by clarifying that max_chars bounds total abstract text on the page, that results are deduplicated by DOI/PMCID, and that next_cursor must be supplied explicitly for another page. It gives a useful Europe PMC syntax example, though it does not further explain limit.

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 ('Search') and resource ('one Europe PMC page for life-sciences articles and abstracts'), and the Europe PMC/abstract scope plus the OpenAlex/XML exclusion separate it from generic literature or article-fetch siblings. It does not explicitly name search_wos, but the source and scope are concrete enough to identify the tool.

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?

The description implies use for Europe PMC life-sciences searches and explains pagination ('Supply next_cursor explicitly for another page'), but it never states when to choose this over search_wos or generic search, nor when not to use it. Guidance is present but largely inferred.

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