Skip to main content
Glama

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

How much paint

paint_calculator
Read-onlyIdempotent

How much paint for a room's walls (and ceiling), minus doors and windows, for a number of coats and primer? Gallons or liters. 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": "paint_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
coatsNo1-10 (default 2).
doorsNoDoors to subtract.
unitsNous (default: ft, in, ft²) or metric (m, cm, m²).
wasteNoExtra percent, 0-50 (default 10).
widthNoRoom width, ft or m.
heightNoWall height, ft or m.
lengthNoRoom length, ft or m.
primerNotrue: add one primer coat.
ceilingNotrue: paint the ceiling too.
windowsNoWindows to subtract.
coverageNoft² per gallon (us) or m² per litre (metric).
doorAreaNoOne door, ft² or m².
wallAreaNoOr the wall area, ft² or m².
windowAreaNoOne window, ft² or m².
ceilingAreaNoCeiling area, ft² or m².
primerCoverageNoPrimer coverage, same units.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 openWorldHint false, so the safety profile is covered. The description adds useful domain context about what is being computed (net wall area minus openings, coats, primer) but never says what comes back — a paint quantity in the chosen unit, presumably — which is the main behavioral gap given there is no output schema.

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 tight and front-load the core question the tool answers. The third sentence is promotional boilerplate pointing at other APIs and is pure noise for an agent selecting or calling this tool, which costs it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 optional parameters and no output schema, the definition should do more to explain the shape of the answer and how the dimension inputs relate to the direct-area inputs. The schema covers individual parameters well, but the description never resolves the either/or between width/length/height and wallArea, nor clarifies defaults beyond what the schema states.

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 all 16 parameters are documented in the schema itself. The description adds semantic framing — that doors and windows are subtracted, primer adds a coat, results come in gallons or liters — but nothing beyond that, such as the wallArea/ceilingArea alternative path to specifying dimensions. Baseline 3 is appropriate when the schema carries the detail.

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 states a specific computation: paint needed for a room's walls and optionally ceiling, subtracting doors and windows, accounting for coats and primer, in gallons or liters. That is far more specific than the name alone and clearly separates it from siblings like concrete_calculator or gravel_calculator. It stops short of naming an alternative, so it lands at 4 rather than 5.

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 which alternative to pick if the request is about something other than paint. Usage is only implied by the calculation being described; an agent must infer the context entirely.

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