Skip to main content
Glama
wos-mcp-bridge

wos-mcp-bridge

Fetch

fetch
Read-onlyIdempotent

Retrieve bibliographic metadata from Web of Science by WOS: accession ID; use it to get record details, not full articles or abstracts.

Instructions

Retrieve bibliographic metadata for a WOS: ID, NOT a full article or abstract.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA WOS: accession ID returned by search, not a DOI or URL.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

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 one useful behavioral fact, that the response is metadata only and will not include article body or abstract, but says nothing about failure modes for invalid or unknown IDs or lookup cost.

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 fourteen-word sentence that front-loads the action and payload, then attaches the discriminating negative clause. Nothing is padded or repeated from the title.

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 one required, fully documented parameter, rich annotations, and an output schema handling return values, the description covers what an agent needs to decide and call. Only minor gaps remain, such as behavior on an unmatched ID.

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 the single parameter already documents the WOS: prefix, pattern, and the 'not a DOI or URL' constraint in its own description. The tool description only echoes the ID framing, adding no syntax or format detail beyond the schema, so baseline 3 applies.

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 (Retrieve) and resource (bibliographic metadata) scoped to a WOS: accession ID, and explicitly negates the full-article/abstract interpretation. That negation cleanly separates it from get_article and get_article_section without needing their schemas.

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?

The phrase 'NOT a full article or abstract' implicitly routes the agent to the article-level siblings when full text is wanted, and the ID format requirement narrows applicability. It stops short of naming an alternative tool or stating what to do with a DOI, so it is clear context rather than a full when/when-not rule set.

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