Skip to main content
Glama

Right cone pattern

bpj_geom_cone
Read-onlyIdempotent

Find slant height, sector angle of the flat pattern, and volume for a right cone.

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

Input Schema

NameRequiredDescriptionDefault
heightYes
radiusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world setting, so the safety profile is fully covered. The description adds value by enumerating the three derived quantities, but says nothing about output units (degrees vs radians for sector angle) or formatting. With annotations carrying the behavioral load, a 3 is appropriate.

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 zero filler; the three outputs are listed up front. It is terse to the point of omitting units and alternatives, but nothing in it 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?

With no output schema, enumerating slant height, sector angle and volume in the description is the right compensation and largely sufficient for a two-input calculator. The remaining gap is the unspecified unit/convention for sector angle and the absence of any positional guidance relative to the cone/frustum siblings.

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, but it only implies the two inputs via "right cone" and never explains their meaning or units. The only real guidance comes from the schema titles ("Radius (m)", "Perpendicular height (m)"), which is structured data the description merely echoes.

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 slant height, sector angle of the flat pattern, and volume" names concrete computed outputs against a specific resource (right cone), so an agent knows exactly what it gets back. The qualifier "right" also distinguishes it from the frustum sibling, though no sibling is named explicitly.

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 statement, no prerequisite, and no pointer to an alternative such as bpj_geom_conical_frustum for a truncated cone. The agent must infer applicability purely from the resource noun.

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.