Skip to main content
Glama
wos-mcp-bridge

wos-mcp-bridge

Get Article Section

get_article_section
Read-onlyIdempotent

Reads a precise JATS article section by section ID with character offsets and bounded text, enabling controlled full-text retrieval without heading guesses.

Instructions

Read one exact JATS section ID, using character offsets and bounded text.

IDs come from get_article. Returns heading, original_id, parent_id, total_chars, truncated and next_offset. Never searches headings heuristically or invents missing text.

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": {
      "identifier": "<identifier>",
      "section_id": "<section_id>"
    },
    "name": "get_article_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoZero-based character offset within the exact section.
max_charsNoMaximum returned text characters; metadata is additional.
identifierYesBare DOI, DOI: prefix, https://doi.org/ URL, PMID digits/PMID:digits, or PMCID PMCdigits; arbitrary URLs and WOS: IDs are rejected.
section_idYesExact section.id returned by get_article; never a guessed section heading.

Output Schema

NameRequiredDescriptionDefault
idYes
doiYes
urlYes
pmidYes
pmcidYes
accessYes
sourceYes
licenseYes
sectionYes
warningsYes
retrievalYes
bibliographyYesAdditive common metadata; null means the authoritative value is unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, open-world call, so the safety profile is covered. The description adds genuine behavioral context beyond that: bounded text with metadata as additional, truncation signalled via 'truncated' and 'next_offset' (i.e., pagination semantics), and the guarantee it will not invent missing text. Listing return field names is partly redundant with the output schema, keeping it off a 5.

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?

Four short sentences, front-loaded with the action and followed by the prerequisite, return shape, and the anti-heuristic constraint. Every sentence carries information, though the enumeration of return fields duplicates the output schema and could be dropped without loss.

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 annotations, a rich 100%-covered schema, and an output schema present, the description covers the remaining gaps an agent needs: where IDs come from, how text is bounded, and how to continue via next_offset. It does not address failure behavior for an invalid or stale section_id, which is the only notable omission for a lookup-by-ID 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 description coverage is 100%, so all four parameters are already documented in the schema, which sets the baseline at 3. The description's 'character offsets and bounded text' frames offset/max_chars as a single paging model, but adds no constraints, units, or edge-case behavior beyond what the schema already states.

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 with scope: 'Read one exact JATS section ID, using character offsets and bounded text.' It also explicitly distinguishes itself from get_article (the source of IDs) and from heuristic heading search, so an agent can tell it apart from its siblings without opening any schema.

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?

'IDs come from get_article' gives an explicit prerequisite and points to the tool that must run first, and 'Never searches headings heuristically' tells the agent not to use this for discovery. Lacks guidance on what to do when the ID is unknown beyond that (e.g., it doesn't name which tool to use for locating a section), but the core when-to-use context is clear.

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