Skip to main content
Glama

Circular sector layout

bpj_geom_circular_sector
Read-onlyIdempotent

Measure arc length and sector area from radius and swept angle.

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

Input Schema

NameRequiredDescriptionDefault
angleYes
radiusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restating. The description adds the useful behavioral fact that two quantities are computed, but it says nothing about units of the results, precision, or handling of edge angles near 0 or 360.

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 and the two output quantities come first. Nothing could be removed without losing information.

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 calculator with no output schema, the description should state what comes back and in what units, since nothing else declares the return shape. It identifies the two computed quantities but stops short of the units and output form an agent needs to use results correctly.

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 carries the burden, and it only restates the two parameter names, glossing 'angle' as 'swept angle'. It does not clarify that the angle is in degrees (that lives only in the schema title) or how radius units propagate into the outputs, leaving the parameter meaning under-specified.

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?

The description states a specific computation (arc length and sector area) and the two inputs that drive it (radius, swept angle). This cleanly separates it from adjacent siblings such as bpj_geom_circle_segment or bpj_geom_chord_radius, though it never names an alternative 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 or when-not-to-use guidance, no mention of prerequisites, and no routing to related geometry tools. The agent must infer the applicable context entirely from the one-line purpose statement.

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.