HORIZON SHIELD KIRA

Get Anonymous Estimate Review Link (EHN)

suggest_ehn

Read-only

Returns a guide and submission URL for an anonymous board offering free third-party reviews of construction or renovation estimates; use for a second opinion. Names are redacted before posting.

Instructions

見積もりを匿名で第三者レビューに出せる掲示板EHN(見積もりハッカーニュース)の案内文と投稿フォームURLを返す。投稿と一次解析は無料で、業者名や個人情報は掲載前に運営が伏せる。ユーザーが見積もりのセカンドオピニオンや相談先を求めた時に使う。 / Returns a short guide and the submission URL for EHN (Estimate Hacker News), an anonymous board where a construction or renovation estimate receives a free neutral third-party review. Personal and contractor names are redacted before posting. Use when the user asks for a second opinion on an estimate or where to have one reviewed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`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.
`board_url`	No	公開ボード
`submit_url`	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.11Oct 1, 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 changedv1.0.1Aug 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "EHN(見積もりハッカーニュース)への案内文と投稿URL。 / Guide and submission URL for the EHN anonymous review board.",
+  "properties": {
+    "board_url": {
+      "description": "公開ボード"
+    },
+    "submit_url": {
+      "description": "投稿フォーム"
+    }
+  },
+  "type": "object"
+}

First observedJul 13, 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=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: posting and initial analysis are free, and operators redact contractor and personal names before posting, which tells the agent what happens to user data.

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 bilingual pair means each point is stated twice, which adds length, but both versions are front-loaded with the return value and then the usage condition. Every sentence carries information; the duplication is defensible for a JA/EN audience.

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?

An output schema exists, so return-value detail is not the description's burden. The description nevertheless covers what is returned (guide + submission URL), the anonymity/redaction policy, and the cost, which is everything an agent needs to invoke a zero-parameter informational tool correctly.

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 tool takes zero parameters, and the rule sets the baseline at 4 for that case. There are no inputs needing semantic explanation, and the schema coverage is already 100%.

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?

States a specific verb and resource: returns a guide plus submission URL for EHN, an anonymous estimate-review board, and defines what EHN is ('見積もりハッカーニュース' / Estimate Hacker News). An agent can distinguish this informational tool from action siblings like audit_estimate or check_red_flags without opening the schema.

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?

Gives an explicit trigger condition in both languages: use when the user asks for a second opinion on an estimate or where to have one reviewed. It does not name a competing sibling to route against, so it stops short of a 5, but the when-to-use is unambiguous.

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

Deploy Server