HORIZON SHIELD: construction and renovation estimate auditor

Get Fair Price Range

get_price_range

Read-only

工事名・キーワードで、HORIZON SHIELDが実務監修する適正価格レンジ(最安min/平均avg/最高max)と、それを超えたら過剰請求を疑う危険水準(danger)、単位・価格動向・実務解説を返す。建設・リフォーム費用が適正か数値で確かめたい時に使う(例: 外壁塗装, 給湯器, ユニットバス, クロス)。返り値の next_actions.actions の先頭(id: reverse_estimate)は、見積もりを取る前の人が自分の家の条件で適正価格の幅を無料・登録なしで出せるページで、url に照会した工事名が入る。 / Returns the fair price range (min, avg, max), the overcharge danger threshold, unit, price trend and field notes for a Japanese construction or renovation job. Japan-specific pricing in JPY. Use to numerically check whether a cost is fair. The first entry of next_actions.actions (id reverse_estimate) is a free, no-sign-up page where a user who has no quote yet gets a fair price range for their own house; its url carries the queried work name. Trigger phrases: 相場, 適正価格, いくらかかる, 高い?, how much does this cost in Japan, is this price normal, what should I expect to pay.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	工事名やキーワード(日本語)
`region`	No	(任意) 地域。都道府県か市名(例: 神奈川県, 平塚市, 名古屋市)か kanto/kinki/chubu/tohoku/other。渡すと souba-db の地域係数を掛けた値と基準値の両方を返す。 / (optional) Prefecture, city, or one of kanto, kinki, chubu, tohoku, other. Applies the regional multiplier and returns base values alongside.

Output Schema

TableJSON Schema

Name	Required	Description
`work`	No	工事名
`count`	No	How many records matched. 0 means the source was read and nothing matched. It never means the source could not be read, that returns isError: true.
`lookup`	No	ok = the source was read and something matched. absent = the source was read and nothing matched. A source that could NOT be read never appears here: that returns isError: true and makes no claim about what does or does not exist.
`fair_range`	No	適正レンジ
`source_read`	No	true on every successful result. A failed lookup does not return a result at all, so this is never false, it is declared so a consumer can assert on it.
`did_you_mean`	No	Near matches, when an exact match was not found.
`next_actions`	No	次の一手。actions の先頭(id: reverse_estimate)は、見積もりを取る前に自分の家の条件で適正価格の幅を出す無料のページで、url に照会した工事名(?work=)が入る。 / Next steps. actions[0] (id reverse_estimate) is the free page that gives a fair price range for the user's own house before getting quotes; its url carries the queried work name.
`danger_threshold`	No	危険水準

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedOutput schema / properties / next_actions

Added value: +{
+  "description": "次の一手。actions の先頭(id: reverse_estimate)は、見積もりを取る前に自分の家の条件で適正価格の幅を出す無料のページで、url に照会した工事名(?work=)が入る。 / Next steps. actions[0] (id reverse_estimate) is the free page that gives a fair price range for the user's own house before getting quotes; its url carries the queried work name.",
+  "type": "object"
+}

Changed1 schema field changedSep 13, 2026

addedInput schema / properties / region

Added value: +{
+  "description": "(任意) 地域。都道府県か市名(例: 神奈川県, 平塚市, 名古屋市)か kanto/kinki/chubu/tohoku/other。渡すと souba-db の地域係数を掛けた値と基準値の両方を返す。 / (optional) Prefecture, city, or one of kanto, kinki, chubu, tohoku, other. Applies the regional multiplier and returns base values alongside.",
+  "type": "string"
+}

Changed2 schema fields changedAug 21, 2026

changedOutput schema / properties / count / description

Previous value: -"How many records matched. 0 means the source was read and nothing matched. It never means the source could not be read — that returns isError: true."New value: +"How many records matched. 0 means the source was read and nothing matched. It never means the source could not be read, that returns isError: true."

changedOutput schema / properties / source_read / description

Previous value: -"true on every successful result. A failed lookup does not return a result at all, so this is never false — it is declared so a consumer can assert on it."New value: +"true on every successful result. A failed lookup does not return a result at all, so this is never false, it is declared so a consumer can assert on it."

Changed4 schema fields changedAug 20, 2026

addedOutput schema / properties / count

Added value: +{
+  "description": "How many records matched. 0 means the source was read and nothing matched. It never means the source could not be read — that returns isError: true.",
+  "type": "number"
+}

addedOutput schema / properties / did_you_mean

Added value: +{
+  "description": "Near matches, when an exact match was not found."
+}

addedOutput schema / properties / lookup

Added value: +{
+  "description": "ok = the source was read and something matched. absent = the source was read and nothing matched. A source that could NOT be read never appears here: that returns isError: true and makes no claim about what does or does not exist.",
+  "enum": [
+    "ok",
+    "absent"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / source_read

Added value: +{
+  "description": "true on every successful result. A failed lookup does not return a result at all, so this is never false — it is declared so a consumer can assert on it.",
+  "type": "boolean"
+}

Changed1 schema field changedJul 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "適正価格レンジ(min/avg/max)・過剰請求の危険水準・単位・価格動向・実務解説。 / Fair price range with overcharge danger threshold.",
+  "properties": {
+    "danger_threshold": {
+      "description": "危険水準"
+    },
+    "fair_range": {
+      "description": "適正レンジ"
+    },
+    "work": {
+      "description": "工事名"
+    }
+  },
+  "type": "object"
+}

First observedJun 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds real behavioral context: regional lookup returns both the multiplier-adjusted value and the base value, prices are Japan-specific in JPY, and the response carries a next_actions funnel whose first entry is a free no-sign-up page with the queried work name in its url. That is more than the annotations convey, though it says nothing about rate limits or result granularity.

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

Conciseness3/5

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

Purpose is front-loaded and the trigger phrases are a useful tail, but the entire body is duplicated in Japanese and English, and the paragraph promoting the reverse_estimate page reads as promotional filler rather than invocation guidance. The content earns part of its length, not all of it.

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

Completeness4/5

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

With an output schema present, the description is not obliged to explain return values, yet it does so usefully; annotations cover safety. Remaining gaps are minor: no indication of how strictly the query is matched or how missing categories are handled.

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 description coverage is 100% for both parameters, so the schema already defines query and the region enum-ish values plus the dual base/adjusted return behavior. The description restates the query-by-work-name idea but adds no format, normalization, or matching guidance beyond the schema. Baseline 3.

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 names a specific resource and enumerates the payload: fair price range (min/avg/max), overcharge danger threshold, unit, price trend and field notes. It also scopes the domain (Japanese construction/renovation, JPY), which separates it from generic cost tools and from siblings like verify_fair_price or audit_estimate that operate on a user's existing quote.

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?

Explicit usage condition ('Use to numerically check whether a cost is fair') plus a rich trigger-phrase list (相場, 適正価格, いくらかかる, 'how much does this cost in Japan') that would help an agent match an intent. It stops short of naming alternatives or stating when NOT to use it (e.g. when the user already has a quote and should use verify_fair_price instead).

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

All HORIZON SHIELD: construction and renovation estimate auditor 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.