Skip to main content
Glama

BAE Batteries USA product catalogue

Read a page or document

fetch
Read-onlyIdempotent

Read the full text of one result from search, find_series or get_documents (a web page, a PDF, or a product series) with its link. A discharge table returns its figures once it has been checked against its datasheet, otherwise the link and page.

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
idYesAn id returned by search, find_series or get_documents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and closed-world, so the description is not responsible for the safety profile. It nevertheless adds non-obvious behavior: the call returns the text plus its link, and a discharge table may return either figures or just the link and page depending on datasheet validation. It omits anything about document size, truncation or paging on long PDFs, which is the main remaining behavioral unknown.

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?

Two tightly packed sentences with the primary action front-loaded and no filler. The second sentence is jargon-dense ('checked against its datasheet') and reads as cryptic rather than clarifying, which keeps it out of the top band.

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?

For a one-parameter read tool with strong annotations and no output schema, the description covers purpose, provenance of the id, and the variable shape of the return (text/link vs. figures). The conditional discharge-table behavior is mentioned but not explained well enough for an agent to predict what it will receive.

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 'id' parameter is already documented as coming from search, find_series or get_documents. The description restates that same provenance without adding format details, so it adds little beyond the schema — the baseline 3 for full schema coverage 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 and object ('Read the full text of one result') and enumerates the sources of that result (search, find_series, get_documents) plus the artifact types (web page, PDF, product series). An agent can immediately tell this is the follow-up read of a search hit rather than another lookup tool.

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?

It clearly establishes the workflow context: the id must come from search, find_series or get_documents, so the agent knows to call those first. It does not state any when-not condition or address the other siblings (quote_request, sizing_tool), so it stops short of full routing guidance.

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.

Resources