Skip to main content
Glama

Oxbox Energy 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.

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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description does add value by naming the content types (web page, PDF, product series) and indicating the link is returned alongside the text. It stays silent on truncation, size limits, or what happens with inaccessible PDFs, which matters for a fetch tool with no output schema.

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?

One sentence, front-loaded with the action and immediately followed by the source constraint and content types. No filler, no redundancy.

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 whose annotations fully describe the safety profile, this is nearly complete: it says what is read, what comes back (full text plus link), and where the id must originate. The only real shortfall is the absence of any note on large documents or failure modes, which the lack of an output schema leaves unaddressed.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that the id must come from search, find_series or get_documents. The description restates the same provenance rather than adding format, validation, or fallback meaning. 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 pairs a specific verb ("Read the full text") with a specific resource ("one result from search, find_series or get_documents") and enumerates the content types handled (web page, PDF, product series). It clearly positions itself as the follow-up reader to the search/discovery siblings, so an agent can distinguish it 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?

It establishes the workflow condition: use this on an id produced by search, find_series or get_documents, which tells the agent it comes after a discovery step. It does not state exclusions or what to do if the document is huge or the id is stale, so the guidance is clear but not exhaustive.

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