Skip to main content
Glama

BAE Batteries USA product catalogue

Link to the online sizing tool

sizing_tool
Read-onlyIdempotent

The link to the online tool BAE Batteries USA offers for sizing a battery system, and where the website links it. The customer runs it themselves; this connector cannot. A starting point only: engineers confirm every size before it is quoted.

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": "sizing_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds meaningful caveats beyond annotations: the customer runs the sizing process, the connector cannot, and the result is only a starting point requiring engineer confirmation.

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 compact and front-loads the core resource. The middle sentence about customer execution is useful context, though the phrasing around 'where the website links it' is slightly awkward.

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 zero-parameter, read-only tool with no output schema, the description gives enough context to call it correctly: what it returns, who uses the linked tool, and the engineering-confirmation caveat. It stops short of specifying the exact URL format, but that is not essential here.

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

Parameters4/5

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

There are no input parameters, so the baseline is 4. The description correctly does not invent parameter semantics and instead focuses on what the zero-parameter call returns.

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 identifies the specific resource returned: a link to BAE Batteries USA's online battery-sizing tool and where the website places that link. It also clarifies that the tool does not perform sizing itself, which helps distinguish it from operational siblings like quote_request or search.

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?

The description implies usage when a customer needs the external sizing tool and explicitly states that the connector cannot run sizing. However, it does not name when to prefer this over siblings such as quote_request or get_documents, so routing guidance remains 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