Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

How much gravel, sand, soil or mulch

gravel_calculator
Read-onlyIdempotent

How much gravel, crushed stone, sand, topsoil or mulch for an area and depth? Volume, weight in tons and bags. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "depth": "<depth>"
    },
    "name": "gravel_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOr the area, ft² or m².
depthYesin or cm.
unitsNous (default: ft, in, ft²) or metric (m, cm, m²).
wasteNoExtra percent, 0-50 (default 10).
widthNoft or m.
lengthNoft or m.
bagSizeNoft³ (us) or litres (metric) per bag.
densityNolb per yd³ (us) or kg per m³ (metric).
materialNoBulk material.

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, non-destructive and closed-world, so safety behavior needs no restating. The description does add useful output context absent from structured fields: results come back as volume, weight in tons, and bag counts. It says nothing about how density/waste defaults affect results, which would have pushed this higher.

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

Conciseness3/5

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

The first two sentences are front-loaded and earn their place. The third is a promotional URL with UTM tracking that gives an agent no information for selecting or invoking the tool and consumes attention.

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?

With nine fully documented parameters, rich enums, and no output schema, the description covers what the tool returns and for which materials, which is the key remaining gap for a numeric estimator. Missing are any notes on unit mixing or how waste/density defaults affect results.

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 100%, so every parameter is already documented, setting the baseline at 3. The description hints that area/depth drive the calculation and that tons and bags are outputs, loosely mapping to density and bagSize, but it adds no format or default detail beyond the schema.

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 names the specific resource (gravel, crushed stone, sand, topsoil, mulch) and what is computed (quantity for an area and depth), which lets an agent distinguish it from concrete_calculator and paint_calculator by material. Phrasing it as a question plus the promotional tail slightly dilutes a crisp verb+resource statement.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the sibling material calculators (concrete, paint) that an agent must choose between. Usage is only implied by the material list.

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.

Resources