remodeleriq

remodeleriq_compare_bids

Read-onlyIdempotent

Compare 2–5 contractor bids for the same project side-by-side. Returns: per-bid confidence scores; a per-trade cost comparison table sorted by price variance; a scope-gap matrix (what Bid A includes that Bid B omits); apples-to-apples adjusted totals (normalizing for scope gaps); outlier detection (trades priced ≥2× or ≤0.5× the median); consolidated red flags across all bids; and a winner recommendation. Use when a homeowner has multiple quotes and wants to know which is best and why.

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": {
      "bids": "<bids>"
    },
    "name": "remodeleriq_compare_bids"
  }
}

Input Schema

Name	Required	Description	Default
`bids`	Yes	2–5 contractor bids to compare side-by-side.

Output Schema

Name	Required	Description
`bids`	Yes
`_meta`	No
`winner`	No
`all_flags`	No	All critical and high-severity flags across every bid.
`bid_count`	Yes
`scope_gaps`	Yes	Trades present in some bids but absent from others, with estimated gap value.
`outlier_flags`	No	Trades where one bid is ≥2× or ≤0.5× the median.
`cost_comparison`	Yes	Per-trade cost table sorted by price variance (largest gap first).
`apples_to_apples`	Yes	Stated total + scope adjustment = adjusted comparable total per bid.

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral specifics: outlier detection thresholds (≥2× or ≤0.5× median), scope-gap normalization, and consolidated red flags, giving an agent a concrete picture of the analysis performed without contradicting annotations.

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?

The description is a single dense sentence with semicolon-separated outputs followed by a one-sentence usage guide. Every clause adds information about what the tool returns or when to use it, with no filler or repetition.

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 one-parameter tool with an output schema, the description covers the action, input constraints, detailed outputs, and the intended use case. It leaves little ambiguity about when to invoke it or what will happen, making it contextually complete.

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

Parameters4/5

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

The schema already covers the bids parameter with 100% coverage, including minItems/maxItems and property descriptions. The description adds the key constraint that bids must be for the same project—not present in the schema description—and references scope-depth normalization, enriching the meaning of the scope_depth field.

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?

The description opens with 'Compare 2–5 contractor bids for the same project side-by-side', providing a specific verb and resource. It then enumerates analytical outputs (confidence scores, scope-gap matrix, outlier detection, winner recommendation) that clearly distinguish it from simpler sibling tools like compare_bids.

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?

The description explicitly states 'Use when a homeowner has multiple quotes and wants to know which is best and why', giving clear when-to-use context. However, it does not mention alternative tools or when not to use, so it lacks explicit exclusions.

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

All remodeleriq 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.