Skip to main content
Glama

Triaxial ellipsoid volume

bpj_geom_ellipsoid
Read-onlyIdempotent

Find ellipsoid volume and areas of all three central principal sections from its semi-axes.

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_ellipsoid"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
cYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds real value by disclosing the exact outputs: volume plus the areas of all three central principal sections. That is the key behavioral fact for a computation tool with no output schema. It stops short of stating output units (m³/m²) or how the sections map to the a-b, a-c, b-c planes.

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 verb first and zero filler; nothing is repeated from the title and nothing could be trimmed 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 three-parameter pure calculator with full annotations and no output schema, the definition is nearly sufficient: it names both outputs and the input family. The remaining gaps are minor but real — output units and the identity of the three section planes are left implicit.

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 must carry parameter meaning, and it only says 'its semi-axes' without mapping a, b, c individually. The schema's own titles ('First/Second/Third semi-axis (m)' with 1e-9 to 1e9 bounds) do most of the work, so the description adds only marginal semantics.

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?

States a specific verb and resource: find ellipsoid volume and the areas of all three central principal sections. Naming 'triaxial' and 'semi-axes' separates it from the sibling sphere/ellipse calculators without the agent needing to open a schema.

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 semi-axes' tells the agent the required inputs, and the calculation nature makes the call context self-evident. There is no explicit when-to-use/when-not, and no sibling such as bpj_geom_sphere or bpj_geom_ellipse is named as an alternative for degenerate (two-equal-axis) cases.

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.