Skip to main content
Glama

get_nerve_lit_article

Retrieve complete metadata for a single peripheral nerve surgery article by its PubMed ID (PMID), enabling quick inspection of the article's details and source coverage.

Instructions

Haal de volledige metadata van één artikel op via zijn PMID.

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": {
      "pmid": "<pmid>"
    },
    "name": "get_nerve_lit_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
pmidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It conveys that a lookup happens and that full metadata is returned, but says nothing about read-only semantics, behavior on an unknown or malformed PMID, or whether results are cached/paginated.

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 front-loaded sentence with no filler; the resource, scope ('één'), and key ('via zijn PMID') appear immediately.

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

Completeness3/5

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

With one required parameter and an output schema, the description needn't explain return values, and 'volledige metadata' covers that adequately. It is still thin on error handling and on how this differs from its two siblings, which matters for correct tool selection.

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 description coverage is 0% — the pmid property has only a title and string type. The description recovers part of that gap by identifying the value as a PubMed ID that selects a single article, but adds no format, length, or validity detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('haal ... volledige metadata van één artikel op') plus the lookup key ('via zijn PMID'), which is unambiguous. It does not name or contrast with search_nerve_lit, so sibling differentiation is left implicit through 'één artikel'.

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 is only implied: 'één artikel' suggests this is the single-record lookup as opposed to a search, but the description never says when to use it instead of search_nerve_lit or get_nerve_lit_stats. No exclusions or preconditions are given.

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