Skip to main content
Glama

Rhombus diagonal layout

bpj_geom_rhombus
Read-onlyIdempotent

Calculate the side, area, and perimeter of a rhombus from its diagonals.

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": {
      "p": "<p>",
      "q": "<q>"
    },
    "name": "bpj_geom_rhombus"
  }
}

Input Schema

NameRequiredDescriptionDefault
pYes
qYes

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the useful behavioral detail that it returns three specific computed values rather than raw input echo. It does not mention precision, rounding, or handling of degenerate inputs where p equals q.

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 the computed outputs first and the required inputs last. No filler, no redundancy.

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 simple closed-form calculator with two required numeric parameters, the definition covers inputs and outputs (side, area, perimeter), which compensates for the absent output schema. Nothing critical is missing, though noting the diagonal-based constraint (both must be positive, per schema bounds) would close the last 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%, so the description should carry meaning; it says 'from its diagonals', establishing that the two inputs are the two diagonals, and the schema titles supply 'First diagonal (m)' and 'Second diagonal (m)'. It does not restate units or clarify which of p/q is which, leaving that to titles alone.

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 ('Calculate') and resource ('rhombus') and enumerates the three derived quantities (side, area, perimeter). It is unambiguous against the sibling geometry tools, which each target a different shape or construct, though it does not explicitly name a sibling to distinguish itself from.

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 rather than stated: 'from its diagonals' tells the agent this is the rhombus entry point when diagonals are known. There is no explicit when-to-use or when-not framing, and no mention of an alternative path (e.g., side-and-angle) if one exists.

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.