Skip to main content
Glama

Hexagonal prism geometry

bpj_geom_hex_prism
Read-onlyIdempotent

Find width across flats, lateral area, and volume of a regular hexagonal prism.

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": {
      "side": "<side>",
      "height": "<height>"
    },
    "name": "bpj_geom_hex_prism"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile needs no restating. The description adds that three specific derived quantities are produced, but says nothing about output units (m, m², m³), numeric precision, or error behavior for out-of-range inputs, so it does not go beyond the minimum.

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?

A single sentence with no filler, and the identifying resource (regular hexagonal prism) is front-loaded. It is efficient but slightly under-informative rather than padded, and the enumerated outputs could be formatted more scannably.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter deterministic calculator with annotations and no output schema, the definition covers what is computed but not the units or form of the returned values, which an agent needs to present results correctly. Adequate, with a clear remaining gap.

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 description coverage is 0%, but the schema does carry titles "Side (m)" and "Perpendicular height (m)" plus min/max bounds. The description contributes meaning by specifying a *regular* hexagonal prism, which fixes "side" as the hexagon edge length, but it never mentions either parameter by name or clarifies their units or geometric role.

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?

"Find width across flats, lateral area, and volume of a regular hexagonal prism" gives a specific verb and resource plus the three returned quantities, so an agent can tell this is a hexagonal-prism calculator rather than a generic polygon tool. Differentiation from siblings comes from the shape name itself; no explicit contrast is offered, so it stops short of a 5.

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?

Usage is implied by the narrow shape name and the listed outputs, but there is no explicit when-to-use statement, no mention of the alternative tools for hexagonal-area-only or general regular-polygon cases, and no stated prerequisites or input constraints beyond the schema.

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.