Skip to main content
Glama

Oxbox Energy product catalogue

List the Oxbox brochures

get_documents
Read-onlyIdempotent

List the documents Oxbox Energy publishes: the Oxbox brochure, as a digital copy (4 pages) and a printable copy (3 pages) of the same text. The specifications are on the brochure's last page. The website publishes no datasheet, SDS, manual or warranty document.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
seriesNoA series id from find_series, or its name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "datasheet",
      -  "discharge_table",
      -  "manual",
      -  "sds",
      -  "certificate",
      -  "standard",
      -  "brochure",
      -  "technical_paper",
      -  "warranty",
      -  "other"
      -]New value: +[
      +  "brochure"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context about the exact brochure formats and the absence of other document types, but it does not describe return structure, pagination, or retrieval behavior.

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?

The description is short, front-loaded, and structured around the document list. The page counts and format distinctions are useful, though some phrasing such as 'of the same text' is slightly more detailed than strictly necessary.

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?

For a simple read-only listing tool with annotations covering safety, the description is reasonably complete about what documents exist. However, given there is no output schema and the series parameter is unexplained, it leaves meaningful gaps for an agent trying to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention either the type or series parameter, nor does it explain how filtering by series changes the result. With only 50% schema description coverage, the description should compensate for the undocumented enum parameter but does not.

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: listing Oxbox Energy's published documents, specifically the brochure in digital and printable formats. It clearly scopes the available documents, but it does not explicitly distinguish this tool from siblings like search or fetch.

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 implied by the document scope and the explicit note that no datasheet, SDS, manual, or warranty document is published, which helps an agent know what this tool will and will not return. However, it gives no explicit when-to-use guidance or named alternatives.

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