Skip to main content
Glama

Closed cylinder geometry

bpj_geom_cylinder
Read-onlyIdempotent

Calculate lateral area, total closed area, and volume for a right circular cylinder.

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": {
      "radius": "<radius>",
      "height": "<height>"
    },
    "name": "bpj_geom_cylinder"
  }
}

Input Schema

NameRequiredDescriptionDefault
heightYes
radiusYes

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=true, idempotentHint=true, destructiveHint=false, and closed-world behavior, which fully covers the safety profile for a pure computation. The description adds only the scope of outputs computed; it says nothing about precision, units, or how open (lateral-only) cylinders are handled.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the outputs are listed compactly and nothing is redundant.

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 calculator with full read-only annotations this is close to sufficient, but with no output schema the description does not say what the return value looks like (single object with three fields?) or its units, leaving a real gap.

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 should compensate, yet it never mentions the two parameters, their units, or the 1e-9 to 1e9 bounds. The only unit information ('Radius (m)', 'Perpendicular height (m)') comes from schema titles, not the description.

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

Purpose5/5

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

Names a specific verb ('Calculate') and resource ('right circular cylinder') and enumerates the three quantities produced: lateral area, total closed area, and volume. The word 'closed' plus the title 'Closed cylinder geometry' distinguishes it from open-shell siblings such as bpj_geom_pipe_shell.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative sibling is named. The agent must infer from the name alone that heavy/other shapes belong to bpj_geom_cone, bpj_geom_pipe_shell, etc.

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.