Skip to main content
Glama

Estimate the cost of a reupholstery job

estimate_job_cost
Read-only

Estimate what reupholstering a piece of furniture costs, broken into labour, fabric, sundries and contingency, with a bench-hours figure. Use this for "how much does it cost to reupholster X", "is it worth reupholstering", and for comparing a professional job against doing it yourself. Distinguishes a modern re-cover (strip to the frame and rebuild in foam and modern materials) from a traditional rebuild (webbing, springs, hair, stitched edges), which is typically two to three times the hours. Returns a range, not a single number, because no two chairs are the same underneath.

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": {
      "piece": "<piece>"
    },
    "name": "estimate_job_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildNoModern re-cover or traditional rebuild. Default modern where available.
pieceYesFurniture type. Options: drop-in dining seat, stuffover dining chair, carver dining armchair, bedroom slipper chair, tub chair, club armchair, wing-back armchair, recliner armchair, loveseat, 2-seat sofa, 3-seat sofa, 4-seat sofa, chaise longue, chesterfield sofa, footstool, window seat cushion, large ottoman, headboard double
currencyNoDefault GBP.
hourly_rateNoWorkshop labour rate. Default 80 (GBP), a typical UK trade rate in 2026.
frame_repairNoLoose joints, broken rails, re-gluing.
deep_buttoningNoAdds 25% to hours and material for buttoning, where the piece allows it.
fabric_price_per_metreNoCost of the chosen cloth per metre. Use 0 if the customer supplies their own fabric.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish this is a safe, closed-world read, so the description's job is to add context beyond that, which it does: it discloses that the result is a range rather than a point estimate and that traditional rebuilds typically cost two to three times the hours. It doesn't explain currency conversion behavior or what the contingency is a percentage of.

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?

Three sentences, front-loaded with the cost breakdown, then use cases, then the mode distinction and range caveat. The parenthetical definitions of modern vs traditional are load-bearing rather than filler.

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

Completeness5/5

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

For a 7-parameter read-only estimator with no output schema, the description covers the essentials: what is returned (categorised cost plus hours), in what form (a range), and the main driver of variance (build type). Nothing an agent needs to invoke it correctly is missing.

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%, so the schema already documents every parameter including defaults, enums and the frame_repair/deep_buttoning flags. The description adds only light framing (bench-hours, the modern/traditional hours ratio) rather than new per-parameter meaning, so the baseline of 3 applies.

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?

Specific verb+resource with an explicit output shape: cost broken into labour, fabric, sundries and contingency plus a bench-hours figure. It also distinguishes two modes (modern re-cover vs traditional rebuild) so an agent can tell what the number means without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete triggering phrasings ("how much does it cost to reupholster X", "is it worth reupholstering") and a comparison use case (professional vs DIY). It stops short of naming alternatives such as calculate_fabric or calculate_deep_buttoning when the agent only needs a component calculation, so no explicit exclusions.

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