Skip to main content
Glama

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

How much concrete

concrete_calculator
Read-onlyIdempotent

How much concrete for a slab, footing, column or stairs? Volume in cubic yards or m³, the ready-mix order and the number of 40/60/80 lb premix bags, with waste. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "concrete_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
runNostairs: in or cm.
riseNostairs: in or cm.
sideNocolumn (square): in or cm.
depthNofooting: in or cm.
shapeNoslab, footing, column or stairs.
stepsNostairs: 1-100.
unitsNous (default: ft, in, ft²) or metric (m, cm, m²).
wasteNoExtra percent, 0-50 (default 10).
widthNoslab, stairs: ft or m; footing: in or cm.
heightNocolumn: ft or m.
lengthNoslab, footing: ft or m.
yield40Noft³ per 40 lb bag (default 0.30).
yield60Noft³ per 60 lb bag (default 0.45).
yield80Noft³ per 80 lb bag (default 0.60).
diameterNocolumn (round): in or cm.
platformNostairs: top landing depth, in or cm.
quantityNoIdentical pieces, 1-1000.
thicknessNoslab: in or cm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that, the description discloses the non-obvious return content (ready-mix volume plus bag counts for three bag sizes) and that a waste percentage is factored in, which is genuinely useful since no output schema exists.

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?

The computational intent and the outputs are front-loaded in two compact sentences with no filler. The trailing 'More APIs from FitzTopPicks' promotional URL does not help an agent decide or invoke the tool and is the one element that fails to earn its place.

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 stateless calculator with 18 optional parameters, the description covers purpose, unit systems and return shape well enough to call it, and the schema documents per-shape parameter roles. The remaining gap is that required parameter combinations per shape (e.g. thickness/width/length for a slab vs. run/rise/steps for stairs) are left entirely to the schema, with no output schema to fall back on.

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% and each parameter already names the shape it applies to and its unit (e.g. 'footing: in or cm', 'slab: in or cm'), so the schema does the heavy lifting. The description adds only the general notion of 'waste' and unit systems, without clarifying which parameter combination is needed per shape.

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?

The description states a specific resource and computation ('How much concrete for a slab, footing, column or stairs') and enumerates the exact outputs (cubic yards/m³, ready-mix order, 40/60/80 lb bag counts). It also implicitly separates itself from the material-based siblings such as gravel_calculator and paint_calculator by naming concrete and premix bags.

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: the shape list ('slab, footing, column or stairs') tells the agent which geometry this tool handles, but there is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives. An agent can infer the domain from the question-form opening, but nothing routes it deliberately.

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