Skip to main content
Glama

Square pyramid geometry

bpj_geom_square_pyramid
Read-onlyIdempotent

Calculate face slant height, side area, and volume of a right square pyramid.

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

Input Schema

NameRequiredDescriptionDefault
sideYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior2/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 is covered. The description adds only the list of computed values and says nothing about output units (the schema titles imply metres but the description never states that results are in metres or squared/cubed units), nor about whether "side area" is one lateral face or the total lateral surface.

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 front-loaded sentence with no filler or redundancy. It is lean to the point of omitting parameter and unit clarification, but nothing in the wording itself is wasted.

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 two-parameter closed-form calculator with full annotation coverage the definition is adequate: inputs are simple numerics and the three outputs are named. It falls short on units of the results and the precise meaning of "side" and "side area", which matter for a measurement tool with no output schema.

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 parameters, yet it never mentions "side" at all and only alludes to height via the word pyramid. It does not say that "side" is the base edge length or that height is the perpendicular apex-to-base distance, details the agent only gets from the schema titles.

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 uses a specific verb ("Calculate") plus a specific resource ("right square pyramid") and enumerates the three returned quantities (face slant height, side area, volume). That distinguishes it clearly from siblings like bpj_geom_cone or bpj_geom_cuboid, though it does not name an alternative explicitly.

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 only implied: an agent can infer this is the tool for pyramid computations from the name and description, but there is no statement of when to prefer a sibling or when the tool is inappropriate. For a self-contained pure calculator that implication is mostly sufficient.

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.