HORIZON SHIELD: Construction Estimate Auditor for Japan (KIRA)

過剰請求の手口スキャン

scan_tactics

Read-onlyIdempotent

ある工事・キーワードに関する『過剰請求の手口』を、HORIZON SHIELD(大賀俊勝30年監修)の検証済みデータ(内部KIRA)から返し、一次ソース(国民生活センター/消費者庁/EHN実例ボード)の在処を添える。価格判定ではなく注意喚起。推測で新事例を断定しない。 / Returns verified overcharge tactics and points to primary sources. Awareness, not a price verdict. USE WHEN: the caller wants the documented overcharge tactics for a work type or keyword, together with their primary sources. DO NOT USE WHEN: the caller has their own quote and wants a verdict on it (call intake_estimate), or wants publishable text (call draft_broadcast). This returns awareness material and never a price verdict on a specific quote.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`work`	Yes	工事名やキーワード(日本語)。例: 外壁塗装, シロアリ, 火災保険

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether tactics were found.
`source`	No	Which server produced this.
`scan_mode`	No	How the set was assembled.
`disclaimer`	No	Awareness material. Not a price verdict on any specific quote.
`primary_sources`	No	Where each tactic is documented publicly.
`verified_tactics`	No	Documented overcharge tactics for the work type.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties

Added value: +{
+  "disclaimer": {
+    "description": "Awareness material. Not a price verdict on any specific quote.",
+    "type": "string"
+  },
+  "ok": {
+    "description": "Whether tactics were found.",
+    "type": "boolean"
+  },
+  "primary_sources": {
+    "description": "Where each tactic is documented publicly.",
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "scan_mode": {
+    "description": "How the set was assembled.",
+    "type": "string"
+  },
+  "source": {
+    "description": "Which server produced this.",
+    "type": "string"
+  },
+  "verified_tactics": {
+    "description": "Documented overcharge tactics for the work type.",
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

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

Changed1 schema field changedJul 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedJun 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows it is safe and idempotent. The description adds value by stating that results are from verified data (KIRA), returns primary sources, and that the tool does not make price verdicts or invent new cases. The description aligns with and complements the 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—only 3 sentences in English plus a brief usage section. Every sentence adds value: the first states what it does and returns; the second clarifies it is awareness only; the third warns against using it for inferences. No wasted words.

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 a single required parameter with 100% schema coverage, a detailed output schema (not shown but present), and strong usage guidance, the description is complete. It covers purpose, inputs, returns, limitations, and alternatives. No gaps remain.

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% and the description already provides a clear example ('外壁塗装, シロアリ, 火災保険') for the single parameter. The description does not add additional constraints or format details beyond the schema example, but the combination is sufficient for the agent.

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 uses specific verbs ('returns', 'points to') and a clear resource (verified overcharge tactics with primary sources). It clearly distinguishes from siblings by stating what the tool does not do: it is for awareness, not a price verdict, and explicitly differentiates from 'intake_estimate' and 'draft_broadcast'.

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 includes explicit 'USE WHEN' and 'DO NOT USE WHEN' sections that name alternative tools ('intake_estimate', 'draft_broadcast') and clarify the tool's scope—documented tactics with sources, not price judgment. This provides clear contextual guidance beyond just purpose.

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.