Skip to main content
Glama

Paint can order

bpj_material_paint_cans
Read-onlyIdempotent

Estimate paint volume and full cans to order using net area, coats, coverage, and can capacity.

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": {
      "area": "<area>",
      "coats": "<coats>",
      "coverage": "<coverage>",
      "can": "<can>"
    },
    "name": "bpj_material_paint_cans"
  }
}

Input Schema

NameRequiredDescriptionDefault
canYes
areaYes
coatsYes
coverageYes

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 readOnly, idempotent, non-destructive, and closed-world, so safety and determinism are covered. The description adds that the result is an order quantity of whole cans, implying rounding, but never states the rounding direction or whether a waste factor applies. It adds modest context beyond the annotations without fully specifying the computation.

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 names the output first and the inputs second, with no filler. It is efficient, though it is arguably too terse given the unstated rounding rule.

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?

For a four-parameter closed-form calculator with no output schema, the description identifies the returned quantities but leaves the rounding rule and the coats/coverage interaction unexplained. An agent can call it correctly but may misinterpret the result.

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 do carry units ('Net area (m2)', 'Coverage (m2/L)', 'Can volume (L)', 'Coats'). The description merely restates those four concepts in prose and adds no new meaning, such as whether coverage is per coat or how coats interacts with area.

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 ('Estimate') and specific outputs ('paint volume and full cans to order'), plus the four inputs used. This is clearly distinguishable from neighboring material calculators such as adhesive spread or brick coverage, though it never explicitly contrasts itself with them.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The only usage signal is the implicit 'to order' framing, which the agent must infer.

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.