BidBud Estimating

Compare quality tiers

compare_tiers

Read-onlyIdempotent

Price the same project at economy, mid-range and premium quality side by side.

Use it when a homeowner asks "what's the difference between a basic and a
high-end job?" or wants to choose a budget level.

Args:
    home_sqft: Finished square footage of the home (200-20000).
    num_rooms: Number of rooms (1-50).
    services: Services to price, e.g. ["flooring", "painting"].
    zip_code: 5-digit US ZIP code of the property, for regional labor pricing.
    state: Two-letter state code, used when the ZIP is unknown.
    stories: Above-grade stories (1, 1.5, 2 or 3; default 1).
    flooring_type: For flooring only: carpet, tile, vinyl, hardwood or mix.
    num_windows: For windows only: actual window count, if known.
    include_permits: Add estimated permit fees.
    include_contingency: Add a 10% contingency allowance.

Returns the total for each tier, a per-service breakdown for each tier, and
each service's totals across the three tiers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`state`	No
`stories`	No
`services`	Yes
`zip_code`	No
`home_sqft`	Yes
`num_rooms`	Yes
`num_windows`	No
`flooring_type`	No
`include_permits`	No
`include_contingency`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.1/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 the safety profile is fully covered. The description adds one genuine behavioral detail, that state is used as a fallback when the ZIP is unknown, but the rest is output-shape detail that duplicates the existing 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.

Conciseness4/5

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

Purpose and usage trigger are front-loaded before the parameter list, and the Args block is dense but readable. It is slightly long and the Returns sentence partially duplicates the output schema, keeping it from a perfect score.

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 10-parameter pricing tool with zero schema description coverage, the description documents every parameter, its constraints and conditionals, and gives usage guidance. With annotations covering safety and an output schema covering returns, nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does so well: it adds value ranges (200-20000 sqft, 1-50 rooms), a concrete example for services, the accepted stories and flooring_type values, default 1 for stories, and conditional semantics (flooring_type only for flooring, num_windows only for windows, state only when ZIP is unknown).

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 opening sentence gives a specific verb (price) and a distinctive scope: the same project across three quality tiers side by side. This clearly separates it from estimate_project or check_quote, though no sibling is named explicitly, so it lands just 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 Guidelines4/5

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

It states when to reach for the tool with a concrete trigger (a homeowner asking about basic vs high-end, or wanting to pick a budget level). There is no explicit when-not clause or named alternative, but the usage context is clear enough that an agent can route correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BidBud Estimating tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?