Skip to main content
Glama

Triangle from three sides

bpj_geom_triangle_three_sides
Read-onlyIdempotent

Use Heron’s formula to find area, inradius, and perimeter from three side lengths.

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>",
      "c": "<c>"
    },
    "name": "bpj_geom_triangle_three_sides"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
cYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, closed-world operation. The description adds useful behavioral context by naming Heron's formula and the three computed outputs, but it does not disclose what happens when the inputs cannot form a triangle or whether an error is returned.

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?

It is a single front-loaded sentence with no wasted words. The method and outputs are stated immediately.

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 three-parameter geometry function with safety annotations, the core computation and outputs are covered. However, the lack of any note about invalid triangles or error behavior leaves an important gap 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%; the properties only have titles indicating first, second, and third side in meters. The description confirms that the three inputs are side lengths, but it does not add constraints such as the triangle inequality, symmetry of arguments, or validity requirements beyond the schema's numeric bounds.

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 outputs: area, inradius, and perimeter from three side lengths. Combined with the tool name, it clearly distinguishes side-side-side triangle solving from siblings such as right_triangle and triangle_sas.

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

Usage Guidelines3/5

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

Usage is implied: call this when three side lengths are known. However, it gives no explicit exclusions or alternatives, and it does not warn that the three lengths must satisfy the triangle inequality.

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.