Skip to main content
Glama
Sign In
PubMed MCP Server

PubMed MCP Server

by Augmented-Nature
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_full_text

Retrieve the full text of a biomedical article from PubMed Central using its PMCID.

Instructions

Retrieve full text from PubMed Central (PMC) when available

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": {
      "pmcid": "<pmcid>"
    },
    "name": "get_full_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
pmcidYesPMC ID (e.g., "PMC1234567" or "1234567")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. 'When available' hints at conditional success, but no details on failure behavior, prerequisites, or side effects.

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?

One efficient sentence with no unnecessary words. Could benefit from slightly more detail, but remains concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should explain return values and error conditions. Only mentions availability, lacking completeness for a simple but conditional tool.

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% and parameter description in schema is adequate. The description adds no extra meaning beyond 'when available', baseline 3 is appropriate.

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?

The description clearly states the action ('Retrieve') and resource ('full text from PubMed Central (PMC)'), and distinguishes it from siblings like 'get_abstract'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No mention of checking availability or fallback options if PMC full text is not available.

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

Deploy Server

Other Tools