remodeleriq

analyze_bid

Read-onlyIdempotent

Deprecated: prefer remodeleriq_analyze_bid. Analyze a home-remodeling contractor's bid/estimate for fairness and risk. Returns a 0-100 confidence score, red flags, a plain-English summary, and negotiation talk tracks. Note: analyses may contribute de-identified data to aggregate remodeling-risk research.

Input Schema

TableJSON Schema

Name	Required	Description
`bid_text`	Yes	The full text of the contractor's bid/estimate (line items, terms, scope).
`bid_total`	No	The total dollar amount of the bid, if known.
`state_code`	No	Two-letter US state code (e.g. 'TX', 'GA') for localized labor/legal context. Defaults to GA.
`finish_tier`	No	Quality tier of finishes specified in the bid.
`scope_depth`	No	Depth of work: cosmetic (paint/fixtures only), pull_and_replace (replace but not reconfigure), full_gut (down to studs), addition (new square footage).
`square_footage`	No	Project area in square feet, if known (e.g. 200 for a bathroom, 400 for a kitchen).

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	No
`summary`	Yes
`verdict`	Yes
`red_flags`	Yes
`missing_items`	Yes
`score_breakdown`	No
`confidence_score`	Yes	0–100 bid confidence score
`negotiation_talk_track`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "_meta": {
+      "type": "object"
+    },
+    "confidence_score": {
+      "description": "0–100 bid confidence score",
+      "type": "number"
+    },
+    "missing_items": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "negotiation_talk_track": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "red_flags": {
+      "items": {
+        "properties": {
+          "detail": {
+            "type": "string"
+          },
+          "fix": {
+            "type": "string"
+          },
+          "flag_id": {
+            "description": "Stable taxonomy ID (e.g. PAY_DEPOSIT_EXCESSIVE)",
+            "type": "string"
+          },
+          "issue": {
+            "type": "string"
+          },
+          "level": {
+            "enum": [
+              "critical",
+              "high"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "level",
+          "issue",
+          "detail",
+          "fix",
+          "flag_id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "score_breakdown": {
+      "properties": {
+        "contract_clarity": {
+          "type": "number"
+        },
+        "contract_weight": {
+          "type": "number"
+        },
+        "final": {
+          "type": "number"
+        },
+        "price_realism": {
+          "type": "number"
+        },
+        "price_weight": {
+          "type": "number"
+        },
+        "scope_completeness": {
+          "type": "number"
+        },
+        "scope_weight": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "verdict": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "confidence_score",
+    "verdict",
+    "summary",
+    "red_flags",
+    "missing_items",
+    "negotiation_talk_track"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedAug 14, 2026

addedInput schema / properties / finish_tier

Added value: +{
+  "description": "Quality tier of finishes specified in the bid.",
+  "enum": [
+    "builder_grade",
+    "mid",
+    "semi_custom",
+    "custom",
+    "luxury"
+  ],
+  "type": "string"
+}

addedInput schema / properties / scope_depth

Added value: +{
+  "description": "Depth of work: cosmetic (paint/fixtures only), pull_and_replace (replace but not reconfigure), full_gut (down to studs), addition (new square footage).",
+  "enum": [
+    "cosmetic",
+    "pull_and_replace",
+    "full_gut",
+    "addition"
+  ],
+  "type": "string"
+}

addedInput schema / properties / square_footage

Added value: +{
+  "description": "Project area in square feet, if known (e.g. 200 for a bathroom, 400 for a kitchen).",
+  "type": "number"
+}

First observedJun 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description goes beyond the read-only/idempotent annotations by noting that analyses 'may contribute de-identified data to aggregate remodeling-risk research,' disclosing a data-collection side effect not covered by annotations. It also specifies the return payload (confidence score, red flags, summary, talk tracks), adding behavioral context. No contradiction with 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 concise, front-loaded with the deprecation warning, and every sentence contributes important information: deprecation, purpose, outputs, and data usage. It is appropriately sized for the tool's complexity.

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?

Given the presence of a full output schema and detailed annotations, the description covers all needed context: what the tool does, what it returns, its deprecation status, and a data-privacy note. No critical gaps remain for an agent to select and invoke the tool correctly.

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?

The input schema already provides 100% coverage of all 6 parameters, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already documents, so it neither improves nor degrades the parameter understanding.

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 clearly states the tool's function with a specific verb and resource: 'Analyze a home-remodeling contractor's bid/estimate for fairness and risk.' It also differentiates from siblings by declaring itself deprecated and pointing to remodeleriq_analyze_bid, making the tool's role unambiguous.

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

Usage Guidelines5/5

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

The description explicitly advises against using this tool by saying 'Deprecated: prefer remodeleriq_analyze_bid.' This provides a clear when-not and names the preferred alternative, fully satisfying the usage guideline criterion.

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.