Skip to main content
Glama

Circle tangent from an outside point

bpj_geom_circle_tangents
Read-onlyIdempotent

Find tangent length and the angle between two tangents from an external point.

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>",
      "distance": "<distance>"
    },
    "name": "bpj_geom_circle_tangents"
  }
}

Input Schema

NameRequiredDescriptionDefault
radiusYes
distanceYes

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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the computed outputs (tangent length and angle), which is useful because there is no output schema, but it omits error behavior for invalid inputs such as distance ≤ radius and does not state angle units.

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 wasted words. It states the computed quantities before any qualifying detail.

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 two-parameter calculator with strong safety annotations and no output schema, the description covers what is computed. However, it leaves out the invalid-input condition (distance ≤ radius), the angle unit (degrees vs radians), and any indication of return structure, which are relevant for correct invocation.

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 carry parameter meaning, but it does not explain either parameter. The schema titles ('Radius (m)', 'Distance to center (m)') provide basic meaning, and the phrase 'external point' implies distance > radius, but this is thin compensation for the coverage gap.

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 verb ('Find') and precise resources ('tangent length and the angle between two tangents from an external point'). It clearly distinguishes what is computed, though it does not explicitly contrast with any sibling tool.

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 guidance, no alternatives, and no explicit prerequisite. The phrase 'from an external point' hints that distance must exceed radius, but this is an implicit geometric precondition rather than actionable usage guidance.

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.