Skip to main content
Glama

Circle from chord and rise

bpj_geom_chord_radius
Read-onlyIdempotent

Recover a circular arch’s radius and central angle from chord and rise.

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": {
      "chord": "<chord>",
      "rise": "<rise>"
    },
    "name": "bpj_geom_chord_radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
riseYes
chordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds no behavioral context beyond the computation itself: it does not state output units (e.g. radians vs degrees for the central angle), assume-valid input constraints (rise must not exceed chord/2), or what happens on geometrically impossible input.

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 no filler; the verb, the resource, and the supporting inputs all appear immediately.

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

Completeness4/5

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

For a two-parameter deterministic geometry function with full annotation coverage and no output schema, naming the two returned quantities is largely sufficient. The remaining gap is output convention, particularly the angular unit of the central angle, which the agent cannot infer from any structured field.

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 supply titles with units ('Sagitta (m)', 'Chord (m)') and bounds. The description names both parameters and implicitly maps 'rise' to the schema's 'Sagitta', adding modest semantic value, but it gives no guidance on valid ranges or the geometric relationship the two must satisfy.

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?

States a specific verb ('Recover') and precise inputs/outputs: radius and central angle from chord and rise. This distinguishes it from siblings like circle_segment or circular_sector by naming the exact geometric inversion it performs, though it does not explicitly name any sibling.

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: the agent must infer 'use when you know a chord length and rise/sagitta and need the radius.' There is no explicit when-to-use, no exclusions, and no pointer to the related sector/segment tools that take a radius or angle instead.

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.