Skip to main content
Glama

Circular segment dimensions

bpj_geom_circle_segment
Read-onlyIdempotent

Calculate chord, sagitta, and circular segment area for the specified sweep.

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>",
      "angle": "<angle>"
    },
    "name": "bpj_geom_circle_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleYes
radiusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, which fully characterizes what is a pure computation. The description adds nothing beyond that - no note on output units, precision, or how sweep is measured - but it does not contradict anything either.

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 compact sentence with the output quantities front-loaded and no wasted wording. Its brevity is appropriate for a single-purpose calculator, though it leaves the parameter relationship implicit.

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, the description usefully enumerates the three returned values (chord, sagitta, area), which is the main completeness win. It still omits output units and the angle convention, gaps that matter for a tool whose only inputs are numeric.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden; it identifies the 'specified sweep' as the key input driving the chord, sagitta, and area results. However, it does not state that the angle is in degrees or that both radius and angle are required, relying on the schema titles for that.

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?

A specific verb ('Calculate') paired with named outputs (chord, sagitta, segment area) and a clearly identified resource ('circular segment'). It is distinguishable from siblings like bpj_geom_circular_sector, though it never explicitly contrasts 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?

No when-to-use guidance, no prerequisites, and no mention of the closely related sector or chord-radius siblings. The agent must infer the appropriate context entirely from the tool name and geometry knowledge.

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.