Skip to main content
Glama

Triangle from two sides and angle

bpj_geom_triangle_sas
Read-onlyIdempotent

Compute the included-angle triangle’s third side and enclosed area.

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": {
      "side": "<side>",
      "base": "<base>",
      "angle": "<angle>"
    },
    "name": "bpj_geom_triangle_sas"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
sideYes
angleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful behavioral fact that the result is a pair of derived values (third side plus area), which matters because there is no output schema. It says nothing about formula, rounding, or units of the returned values.

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 computed outputs are named immediately. Nothing is wasted or buried.

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 pure-computation tool with no output schema, naming the two returned quantities is the right minimum, and it does that. However, it leaves the agent to infer output units and whether the third side is the side opposite the included angle, which for a SAS solver is a real gap.

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%, though the schema titles do carry units (m, deg) and bounds. The description's one contribution is "included-angle," which clarifies that the angle lies between the two given sides, resolving the main ambiguity in the schema. It does not explain why both "base" and "side" are needed or how they differ.

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?

States a specific verb ("Compute") and a specific result set ("third side and enclosed area") for an included-angle triangle, which is concrete enough to distinguish it from a generic triangle tool. It does not explicitly name the side-side-side sibling, so the differentiation from bpj_geom_triangle_three_sides is only implied by "included-angle".

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 mention of the alternative triangle tools, and no stated preconditions beyond the implicit requirement of two sides and the angle between them. An agent must infer the selection criteria from the name alone.

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.