HORIZON SHIELD: Construction Estimate Auditor for Japan (KIRA)

見積もり適正診断(KIRA)

intake_estimate

Read-onlyIdempotent

施主の建設・リフォーム見積もりを受け付け、HORIZON SHIELD KIRA(内部・中立)の適正価格診断へ橋渡しする集客窓口。工事名と業者提示額を渡すと、適正かどうかの判定と、無料の第三者チェック(EHN)への導線を返す。価格の断定はせず、確認すべき点を渡す。 / Intake desk: bridges a homeowner quote to the KIRA fair-price audit and returns the verdict plus a free third-party check (EHN) path. USE WHEN: a homeowner has a specific quoted price for a named construction or renovation work item in Japan and wants to know whether that price is reasonable. DO NOT USE WHEN: there is no price yet (call ask), the caller wants the known overcharge tactics rather than a verdict on their own quote (call scan_tactics), or the caller wants publishable text (call draft_broadcast). Returns a verdict and a free third-party check path. It does not draft or post.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`work`	Yes	工事名(日本語)。例: 外壁塗装シリコン
`quoted_price`	Yes	業者提示の金額(円)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the quote was accepted for audit.
`next`	No	Suggested follow-up tools or paths, including the free third-party check.
`audit`	No	The fair-price verdict from the internal KIRA audit.
`source`	No	Which server produced this.
`message`	No	Reason when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties

Added value: +{
+  "audit": {
+    "additionalProperties": true,
+    "description": "The fair-price verdict from the internal KIRA audit.",
+    "type": "object"
+  },
+  "message": {
+    "description": "Reason when ok is false.",
+    "type": "string"
+  },
+  "next": {
+    "description": "Suggested follow-up tools or paths, including the free third-party check.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "ok": {
+    "description": "Whether the quote was accepted for audit.",
+    "type": "boolean"
+  },
+  "source": {
+    "description": "Which server produced this.",
+    "type": "string"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "ok"
+]
```

Changed2 schema fields changedJul 18, 2026
- addedInput schema / properties / quoted_price / minimum
```
Added value: +0
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedJun 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds behavioral context: it returns a verdict and a free third-party check path, does not assert price definitively, and does not draft or post. This provides useful nuance beyond the annotations, though it does not discuss response formats or rate limits.

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?

The description is well-structured: a concise purpose statement in both Japanese and English, followed by explicit usage guidelines and a clear statement of what it returns and does not do. It is slightly verbose due to bilingual repetition, but every sentence adds value and the critical information is front-loaded.

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 tool with only two required parameters and an output schema, the description covers all necessary context: the tool's purpose, exact input requirements, usage boundaries, and behavioral constraints (no drafting, no price finality). The presence of an output schema means the return structure does not need to be elaborated in the description.

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% (both work and quoted_price have detailed descriptions). The description re-emphasizes that work is a named construction item in Japan and quoted_price is the contractor's quoted amount, but adds minimal new semantic information beyond the schema. Baseline 3 is appropriate as the schema already handles parameter documentation.

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 role as an intake desk that accepts a homeowner's quote (work name and price) and returns a fairness verdict plus a path to a third-party check. It uses specific verbs ('bridges', 'returns') and resource ('KIRA fair-price audit'). It distinguishes from siblings by explicitly naming alternatives (ask, scan_tactics, draft_broadcast) in the DO NOT USE section.

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?

Provides explicit USE WHEN and DO NOT USE conditions: use when a homeowner has a specific quoted price for a named construction item in Japan; avoid when no price yet (call ask), when wanting overcharge tactics (call scan_tactics), or when wanting publishable text (call draft_broadcast). Also notes it does not draft or post, which helps the agent rule out incorrect usage.

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 Estimate Auditor for Japan (KIRA) 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.