Skip to main content
Glama

Rectangular box geometry

bpj_geom_cuboid
Read-onlyIdempotent

Find surface area, volume, and body diagonal of a rectangular box.

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": {
      "width": "<width>",
      "depth": "<depth>",
      "height": "<height>"
    },
    "name": "bpj_geom_cuboid"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthYes
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. Beyond that, the description adds the meaningful fact that three specific derived quantities are returned, which matters because no output schema exists.

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?

One short sentence, front-loaded with the verb and ending with the returned quantities; there is no filler. It is arguably too terse for a tool whose schema is undocumented, but nothing in it is wasteful.

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 simple pure-calculation tool whose annotations already establish it as a safe read with no side effects, the definition covers what is computed and implies determinism. The remaining gaps (output units such as m²/m³/m and the degenerate-input lower bound of 1e-9) are modest for a tool of this complexity.

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 description coverage is 0%, so the description carries the burden of clarifying the three parameters, but it adds nothing. It never says that width, depth, and height are the rectangular-box edge lengths in metres, nor how the body diagonal relates to them; only the schema titles ('Depth (m)', 'Perpendicular height (m)') supply units and meaning.

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 gives a specific verb ('Find') and resource ('rectangular box') and enumerates the exact outputs: surface area, volume, and body diagonal. The shape name distinguishes it from the many other geometry siblings (sphere, cone, cylinder), though it never explicitly contrasts itself with them.

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 when-to-use or when-not-to-use guidance, and no mention of assumptions such as orthogonal faces or unit consistency. The agent must infer the calling context entirely from the shape name.

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.