Skip to main content
Glama

Estimate a countertop job

estimate_job
Read-onlyIdempotent

Estimate total cost from countertop square feet: install at the posted rate plus slabs. Assumes about 75% of each slab is usable.

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": {
      "sqft": "<sqft>"
    },
    "name": "estimate_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqftYesCountertop square feet (length x depth in inches / 144, summed)
slab_sqftNoSquare feet per slab; defaults to 55 (about 126 x 63 in)
slab_price_usdNoPrice per slab; defaults to the $999 Budget Collection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read. The description adds real behavioral context the annotations cannot: the 75% slab utilization assumption that drives the result, and that install pricing comes from a 'posted rate'. It omits whether the output is a bare total or a breakdown, so it is not a 5.

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

Conciseness5/5

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

Two tight sentences with no filler; the cost formula is front-loaded and the key modeling assumption follows immediately.

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 three-parameter calculation tool with no output schema, the definition should indicate what is actually returned (a single total, a line-item breakdown of install vs. slab cost, or caveats about taxes/labor). The waste-factor disclosure is the most important missing-context piece and it is present, but the return shape remains undocumented.

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 coverage is 100%, with defaults documented for slab_sqft and slab_price_usd, so the schema does the heavy lifting. The description's only added semantics is the 75% usability factor, which is useful context for interpreting slab math but does not clarify any individual parameter 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?

States a specific verb ('Estimate') and a precisely scoped resource ('total cost from countertop square feet'), plus the cost components (install rate + slabs). It is distinguishable from quote-generation siblings by framing, though it never names an alternative explicitly.

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. An agent must infer from the word 'Estimate' that this is a rough costing path rather than a formal quote (generate_quote/request_quote), and nothing states the tradeoff between the two.

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