Skip to main content
Glama

Right triangle layout

bpj_geom_right_triangle
Read-onlyIdempotent

Find the hypotenuse, acute angles, and area for two perpendicular legs.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "bpj_geom_right_triangle"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare this a safe, idempotent, closed-world read, so the description needn't repeat that. It adds value by disclosing what comes back — hypotenuse, two acute angles, and area — which matters since there is no output schema, though it omits whether angles are degrees or radians and what precision to expect.

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 sentence with zero filler, front-loading the outputs and closing with the input condition. 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.

Completeness4/5

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

For a two-parameter pure computation with no output schema, this covers the essentials: what inputs mean geometrically and what results to expect. The only real gap is output units for the angles and lengths, which an agent would want when interpreting results.

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%, so the schema contributes only titles ('Width (m)', 'Perpendicular height (m)'). The description adds the meaningful clarification that the two values are the perpendicular legs rather than a hypotenuse, but it does not explain the width-versus-height roles or how the pair is oriented beyond what the titles imply.

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?

The description names a specific computation and its exact outputs (hypotenuse, acute angles, area) and the exact input condition (two perpendicular legs). That distinguishes it cleanly from the sibling triangle tools that take side-angle-side or three sides, without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for two perpendicular legs' implicitly tells the agent when this tool applies: you have two legs at a right angle. There is no explicit exclusion or naming of alternatives such as bpj_geom_triangle_sas, so routing is clear but not fully spelled out.

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.