Skip to main content
Glama

Oxbox Energy product catalogue

Find a battery series

find_series
Read-onlyIdempotent

Return the Oxbox, the one product Oxbox Energy offers (48 V, VRLA gel tubular plate, for solar and home backup), with its page and brochure.

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

Input Schema

NameRequiredDescriptionDefault
textNoWords from the series name or model, e.g. "Oxbox"
voltageNoNominal voltage, e.g. "48 V"
chemistryNoe.g. gel, tubular plate
applicationNoe.g. solar, home backup
include_discontinuedNoInclude series the site marks as discontinued (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / application / description
      Previous value: -"e.g. telecom, utility, solar, UPS, switchgear"New value: +"e.g. solar, home backup"
    • changedInput schema / properties / chemistry / description
      Previous value: -"e.g. gel, AGM, flooded, pure lead, lithium"New value: +"e.g. gel, tubular plate"
    • changedInput schema / properties / text / description
      Previous value: -"Words from the series name or model, e.g. \"OPzV\" or \"NSB 190FT\""New value: +"Words from the series name or model, e.g. \"Oxbox\""
    • changedInput schema / properties / voltage / description
      Previous value: -"Nominal voltage, e.g. \"12 V\""New value: +"Nominal voltage, e.g. \"48 V\""
  2. First observed

TDQS

C2.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description contributes one genuinely useful behavioral detail with no output schema to carry it: results include the product page and brochure. It says nothing, however, about how filtering or the discontinued toggle affects what comes back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with the return content stated early, which is good structure. The long parenthetical of product specs consumes most of the text without adding selecting or invocation value, so the words are doing the wrong job rather than too much of the right one.

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 no-annotation-burden read-only lookup with full schema coverage, the definition covers the essentials: what comes back (series plus page and brochure) and the domain it applies to. The main gap is that include_discontinued and the interaction between multiple optional filters are never addressed.

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?

Schema coverage is 100%, so the baseline would be 3, but the description does not merely stay silent — it presents "48 V, VRLA gel tubular plate, for solar and home backup" as fixed attributes of one product rather than as the filterable inputs (voltage, chemistry, application) the schema defines. That framing actively works against understanding the parameters instead of reinforcing them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence does name a verb and a resource ("Return the Oxbox ... with its page and brochure"), but it frames a five-filter search tool named find_series as a single-product fetch of one known item. An agent reading only this would not realize it is a series lookup that can be narrowed by text, voltage, chemistry, application, or discontinued status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no routing to alternatives such as fetch or search, even though returning a page/document strongly overlaps with fetch. The only implicit cue is the product spec list, which hints at solar/home-backup queries but never states the condition that selects this tool.

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