Skip to main content
Glama

BAE Batteries USA product catalogue

List datasheets, manuals, SDS and discharge tables

get_documents
Read-onlyIdempotent

List the documents BAE Batteries USA publishes for a series, or of one type across the site: datasheets, discharge tables, installation and operating manuals, safety data sheets, ISO certificates, technical papers and flyers. Third-party documents (HindlePower charger manuals) are linked at their source.

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: +[
      +  "datasheet",
      +  "discharge_table",
      +  "manual",
      +  "sds",
      +  "certificate",
      +  "brochure",
      +  "technical_paper",
      +  "other"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds only the third-party linking behavior and document scope; it does not describe pagination, return format, or auth requirements, so the extra context is useful but limited.

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?

Two sentences, front-loaded with the purpose, and the enumeration of document types is necessary to convey scope. No promotional or redundant wording is present.

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?

The tool is simple and its read-only safety profile is already in annotations, but the description leaves the no-parameter behavior and result structure unstated. With no output schema, that is a meaningful gap for an otherwise clear list 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?

The schema covers the series parameter and type enum, but the description adds meaning by naming the document categories and distinguishing a series-scoped query from a site-wide type query. It does not resolve the enum's "brochure"/"other" values or explain how series and type combine, or what no-argument behavior does.

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 opens with a clear specific verb, "List," and resource, "documents BAE Batteries USA publishes," then enumerates the document categories and scopes them to a series or one type across the site. It does not explicitly name siblings such as search or find_series, so it stops short of full sibling differentiation.

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?

It identifies two modes (for a series or one type across the site) and notes that third-party charger manuals are linked at source, which implies when the tool is useful. It does not state when to use search or fetch instead, or what happens with no filter, so the guidance is only implicit.

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