Skip to main content
Glama

Pubtator Search

pubtator_search
Read-onlyIdempotent

Search PubMed/PMC literature by biomedical entity and get back, for each paper, the sentence that matched with its entity mentions decoded (gene, disease, chemical, variant, species, cell line, each normalized to an id). Query by plain text ("metformin alzheimer"), by PubTator entity ids combined with AND/OR ("@GENE_BRCA1 AND @DISEASE_Breast_Neoplasms"), or by a relation ("relations:treat|@CHEMICAL_Doxorubicin|@DISEASE_Breast_Neoplasms"). 10 results per page; total count and page count returned. Sourced from the PubTator 3 search index at NCBI/NLM (~36M PubMed abstracts + PMC open-access full text). Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page": 1,
      "query": "@GENE_BRCA1 AND @DISEASE_Breast_Neoplasms"
    },
    "name": "pubtator_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1-based (default 1). 10 results per page.
queryYesFree text, or PubTator entity ids joined with AND / OR (e.g. "@GENE_BRCA1 AND @DISEASE_Breast_Neoplasms"), or a relation query "relations:<type>|<entity1>|<entity2>". Get ids from pubtator_find_entity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful operational facts: 10 results per page, total/page counts returned, keyless access, and the upstream index behind it. It does not cover retrieval limits, ranking, or error behavior, but it goes beyond the annotations.

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?

A single dense paragraph that front-loads what the tool does and its output shape, then the accepted query forms, then pagination/source/keyless facts. Every sentence carries information; no 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?

With no output schema, the description usefully characterizes the return value (matching sentence plus decoded, id-normalized entity mentions) and explains pagination and total counts. Only edge details, such as result caps or behavior when a query matches nothing, are missing.

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 100%, so the schema already documents both parameters in near-identical terms. The description elaborates the query grammar with examples, but those forms are already present in the schema, so it adds little meaning beyond duplication.

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 PubMed/PMC literature") plus the exact shape of the return (per-paper matching sentence with decoded entity mentions normalized to ids). The three supported query modes and the data source (~36M abstracts + PMC OA) make the scope unmistakable and distinguishable from a plain literature search.

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 guidance on how to query (free text, entity-id boolean, relation syntax) and the schema points to pubtator_find_entity for obtaining ids. It does not state when to prefer it over siblings like pubtator_relations or pubtator_annotations, but the described behavior makes the intended context clear.

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.