Skip to main content
Glama

Tapered planter soil volume

bpj_material_soil_planter
Read-onlyIdempotent

Find soil litres from the inside bottom diameter, inside diameter at the fill line, and fill height of a tapered round planter.

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

Input Schema

NameRequiredDescriptionDefault
topYes
bottomYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 a closed-world scope, so the safety profile is fully covered. The description adds that the result is expressed in litres, which matters since there is no output schema, but says nothing about the taper model assumed (linear frustum), rounding, or handling of inverted diameters.

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 front-loaded sentence that states the output first and then the three inputs, with no filler. Slightly awkward phrasing ('Find soil litres from...') but nothing wasted and nothing buried.

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-math calculator with full annotation coverage and no output schema, the description covers the essential contract: inputs in mm, output in litres, geometry being a tapered round planter. Only the taper assumption and unit flexibility are left unstated, which is a minor gap at this complexity.

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%, but the schema titles already read 'Inside bottom diameter (mm)', 'Inside diameter at fill line (mm)' and 'Fill height (mm)', and the description essentially restates those three in prose. It confirms the mm-in/litres-out contract and the inside-measurement convention, but adds no new constraint or unit-conversion nuance.

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-and-resource pair: computing soil litres for a tapered round planter from three dimensions. It is clearly distinct from most siblings (board feet, paint cans, seed spacing), though it does not name the nearest alternative such as loose fill, leaving that differentiation to the caller.

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 only implied by the physical scenario described (a tapered round planter being filled with soil). There is no explicit statement of when to pick this over a sibling volume or fill calculator, and no prerequisites or exclusions.

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.