Skip to main content
Glama

BAE Batteries USA product catalogue

Search BAE Batteries USA

search
Read-onlyIdempotent

Search the BAE Batteries USA website for stationary batteries, chargers and DC power: its pages and their datasheets, discharge tables, installation and operating manuals, SDS, ISO certificates and technical papers. Ask in plain words, e.g. "12 V gel battery for solar" or "OPzS 2V cell SDS". Returns ids, titles and source links; read one with fetch.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for.

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape ("ids, titles and source links") and the intended two-step search-then-fetch workflow. It omits pagination/result-count limits, which keeps it from a 5.

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 verb and scope are front-loaded and every sentence carries information: corpus scope, query style, examples, return shape, and next step. The first sentence is long due to the document-type enumeration, but each item genuinely narrows what the agent can expect to find, so little is wasted.

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 single-parameter read-only search with no output schema, the definition covers what is searched, how to phrase the query, what comes back, and how to continue. The only gap an agent might care about is result volume/pagination behavior, which is minor at this complexity.

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 query parameter is already documented as "What to look for." The description does add meaningful guidance that the query is natural-language ("ask in plain words") with example phrasing, which is more than the schema conveys, but for a one-parameter tool this remains close to the baseline.

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?

"Search the BAE Batteries USA website" names a specific verb and resource, and the enumeration of content types (pages, datasheets, discharge tables, manuals, SDS, certificates, papers) defines the corpus precisely. The closing "read one with fetch" makes the relationship to the retrieval sibling explicit, so an agent can distinguish search from fetch without inspecting either 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 gives concrete usage context with two worked example queries ("12 V gel battery for solar", "OPzS 2V cell SDS") and states the plain-language input expectation. It also routes the follow-up step to fetch. It stops short of stating when not to use it or how it differs from siblings like get_documents or find_series, so it is clear context without exclusions.

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