Skip to main content
Glama

Oxbox Energy product catalogue

How to request system sizing

sizing_request
Read-onlyIdempotent

Oxbox Energy has no online sizing tool, and this connector cannot size a system. This says how to get one sized: the customer sends the load, runtime and voltage with a quote request and the engineers size it.

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_request"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent, closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: there is no online sizing tool and this connector performs no sizing, which manages agent expectations about capability limits. It could go further on what the tool actually returns instead of only the downstream process.

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?

It is a single compact statement with the most important fact — that sizing is impossible here — front-loaded. The phrase "This says how to get one sized" is slightly self-referential and could be folded into the surrounding sentences without losing meaning.

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 informational tool with no output schema, the description covers the essential facts: no sizing capability, and the exact inputs an engineer needs to perform sizing. The only gap is naming the sibling tool to invoke next, which the agent must infer.

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?

The schema has zero parameters and full coverage, so the baseline is 4. The description correctly implies no inputs are needed; the load, runtime and voltage values are for the subsequent quote request, not for this tool.

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 informational purpose — explaining how to obtain a system sizing — and opens by declaring the limit ("this connector cannot size a system"), which prevents an agent from mistaking it for a calculation tool. It implicitly separates itself from quote_request by describing the sizing path. A slightly tighter framing of what the tool returns would make the purpose unambiguous versus its siblings.

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 a clear trigger (a customer needs a system sized) and the concrete path forward: send load, runtime and voltage with a quote request. It does not explicitly name the quote_request sibling or state when not to call this tool, so the routing is implied rather than spelled out.

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