Skip to main content
Glama

Ellipse area and perimeter estimate

bpj_geom_ellipse
Read-onlyIdempotent

Compute area, focal separation, and Ramanujan’s approximate perimeter from the semi-axes.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "bpj_geom_ellipse"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context by naming the three computed quantities and disclosing that the perimeter is Ramanujan's approximation, but it does not describe approximation accuracy or edge-case behavior.

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. It efficiently names the operation and all three outputs.

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 simple two-parameter pure calculation with rich safety annotations and no output schema, the description is nearly complete: it names all three returned quantities and the approximation used for perimeter. It is slightly incomplete because it omits usage routing and explicit parameter-to-axis mapping.

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 must compensate for undocumented parameters. It only says 'from the semi-axes' and does not map a/b to semi-major versus semi-minor axes or explain constraints, leaving the schema titles to carry nearly all parameter meaning.

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?

States a specific verb (compute) and names the precise outputs: area, focal separation, and Ramanujan approximate perimeter from the semi-axes. This clearly identifies an ellipse calculation and distinguishes it from sibling geometry tools like ellipsoid or circle-segment calculations.

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?

The description gives no explicit when-to-use guidance, no exclusions, and no alternatives. It implies a pure ellipse calculation, but it does not help an agent choose between this and related geometry tools such as ellipsoid or annulus.

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.