Skip to main content
Glama

Trapezoidal plot

bpj_geom_trapezoid
Read-onlyIdempotent

Find the midline and area of a plot from parallel edges and their perpendicular separation.

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": {
      "base": "<base>",
      "top": "<top>",
      "height": "<height>"
    },
    "name": "bpj_geom_trapezoid"
  }
}

Input Schema

NameRequiredDescriptionDefault
topYes
baseYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is fully covered by structured fields. What the description adds beyond them is the return content (midline and area), which matters because no output schema exists; it does not cover precision, rounding, or behavior when base and top are equal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the outputs and the inputs front-loaded and no filler. Nothing is vestigial, though the phrase "of a plot" is domain flavor rather than information an agent needs to call the tool.

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-required-number calculator with no output schema, the description states what is computed and from what, which is adequate. It leaves gaps on units confirmation (meters appear only in schema titles), whether base/top ordering matters, and what exactly the returned midline/area pair looks like.

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%, and the schema's own titles ("Base (m)", "Other parallel edge (m)", "Perpendicular height (m)") already supply most of the meaning. The description's "parallel edges and their perpendicular separation" maps loosely onto base/top/height but does not clarify whether base must be the longer edge or that order is interchangeable, which is the main ambiguity for a 3-parameter trapezoid.

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 gives a specific verb ("Find") and resource ("midline and area of a plot") plus the inputs it derives them from ("parallel edges and their perpendicular separation"). That grounds it as a trapezoid geometry calculator, distinguishing it in substance from bpj_pairs_trapezoid_integral, though it never names the sibling to make the split explicit.

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 or when-not-to-use guidance and no reference to an alternative such as the trapezoid integral tool. The only guidance is implicit in the input phrasing, which an agent must infer from the geometry wording 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.