Skip to main content
Glama

Craft Quantities: construction material calculators

Level two to six quotes for one job, line by line

level_quotes
Read-onlyIdempotent

Levels two to six contractors' quotes for one job against the job's own lines: per line, whether each includes it (its quantity against the job's range, both systems), leaves it out, excludes it or offers an alternative; what each adds; questions to ask. Money is taken out: no total, no ranking.

Input Schema

NameRequiredDescriptionDefault
jobYesThe job the quotes are for: a quote check (bathroom-quote, plastering-quote, concrete-slab-quote …) or a takeoff id that has one.
detailNofull (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.full
marketNoOptional. A market whose own opening choice some inputs take (a UK reader's code, an IEC motor), and whose currency symbol prints the caller's own money figures.
quotesYesTwo to six quotes for the same job. Money in them is taken out before reading.
systemNoThe unit system inputs left out open in, and the one the page link opens in. The answer comes in both.metric
selectionNoBuild-up choice id → option id, the takeoff's own (a stud size, an insulation, a cladding). Choices left out take the page's own for the system.
inputUnitsNoSend "base" to pass bare numbers on dimensioned inputs in base units (m, m², L, kg …), as the published test vectors are written. Without it a length, area or volume must carry its unit.
measurementsNoMeasurement id → value, each length, area or volume with its unit ("12 ft", {"value": 3.6, "unit": "m"}); counts as numbers. Ids are those of the takeoff; any left out opens at the page's own figure.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish a safe, read-only, idempotent, closed-world operation. The description adds meaningful behavioral context beyond that: money is stripped out, no total or ranking is produced, and the output covers inclusion status, additions, and follow-up questions. It does not describe return format or pagination, but the 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 description is compact and front-loads the main action before listing per-line details. The sentence is dense with semicolons but every clause contributes to understanding the comparison output.

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 complex tool with eight parameters, nested objects, a full output schema, and annotations, the description covers the core behavior and the important money-removal caveat. It is somewhat thin on when to choose this over sibling tools, but the structured fields fill in the rest.

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 the schema already documents all eight parameters thoroughly. The description adds little beyond what the schema provides, beyond reinforcing 'both systems' and the two-to-six quote scope. Baseline 3 is appropriate when the schema carries parameter semantics.

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 action ('Levels... quotes') and resource ('contractors' quotes for one job against the job's own lines'), and it details the per-line dimensions compared. It does not explicitly distinguish itself from siblings such as check_quote or compare_on_job, so it stays short of a 5.

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?

The context implies this is for comparing two to six quotes for a single job line by line, and the schema enforces the quote count. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives like check_quote or compare_on_job.

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