Skip to main content
Glama

Fillet between two edges

bpj_geom_offset_fillet
Read-onlyIdempotent

Calculate tangent setbacks, center offset, and arc length for a fillet inside a corner.

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>",
      "interior": "<interior>"
    },
    "name": "bpj_geom_offset_fillet"
  }
}

Input Schema

NameRequiredDescriptionDefault
radiusYes
interiorYes

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 the tool as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value by naming the three computed outputs, which matters since there is no output schema. It does not mention units, assumptions, or failure conditions beyond what annotations provide.

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; every clause contributes either the outputs or the domain (fillet in a corner).

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 two-parameter pure calculation with strong annotations, the definition is serviceable: it states what is computed and the geometric context. It is incomplete in that it does not define the corner-angle convention or confirm that results are in meters/degrees, and there is a slight framing mismatch between the title ('between two edges') and the description ('inside a corner').

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% and the description adds essentially no parameter meaning beyond schema titles. It does not clarify that 'interior' is the corner angle in degrees or that 'radius' is the fillet radius in meters; those details live only in the schema titles/constraints, and the description leaves the geometric interpretation implicit.

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 names a specific computation (tangent setbacks, center offset, arc length) for a fillet in a corner, so an agent can tell this is a geometry calculation rather than a lookup or conversion. It does not explicitly contrast with sibling geometry calculators, but the fillet-specific output list is distinctive enough.

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 explicit statement of when to use this tool, prerequisites, or alternatives. Usage is only implied by 'for a fillet inside a corner' — the agent must infer that it applies when modeling a rounded interior corner.

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.