Skip to main content
Glama

HORIZON SHIELD YAKUMO (verified contractor directory)

by io.github.ogasurfproject-jpg
OverviewDiscussionsAdmin

検証済み加盟店の一覧

list_verified_stores
Read-onlyIdempotent

Yakumo モールで検証を通過した加盟店(工務店・リフォーム店)を一覧する。適正価格の検証と過剰請求チェック(KIRA)を通過した店だけが返る。area(地名)や work(工種)で絞り込める。返り値は member_no / 会社名 / 地域 / 対応工種 / 適正度スコア / 誠実度ティア / プロフィールURL。金額は含まない(スコアとティアのみ)。検証手続き中の店は verification:'pending' として区別される。Japan only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo地名で絞り込み(例: 愛知県, 長久手市)。省略で全件。
workNo工種で絞り込み(例: 外壁塗装, 屋根, 内装)。省略で全件。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
roster_readNotrue = the contractor roster was read successfully; any counts below are real facts about the roster. false = the roster could NOT be read, and this response makes no claim about how many contractors exist. A count of 0 with roster_read true means nobody matched. There is no case where a failed read reports a count.
pending_countNo
roster_sourceNo
verified_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties
      Added value: +{
+  "pending_count": {
+    "type": "number"
+  },
+  "roster_read": {
+    "description": "true = the contractor roster was read successfully; any counts below are real facts about the roster. false = the roster could NOT be read, and this response makes no claim about how many contractors exist. A count of 0 with roster_read true means nobody matched. There is no case where a failed read reports a count.",
+    "type": "boolean"
+  },
+  "roster_source": {
+    "enum": [
+      "kv",
+      "published",
+      "none"
+    ],
+    "type": "string"
+  },
+  "verified_count": {
+    "type": "number"
+  }
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior; the description adds useful details such as pending verification status ('verification:'pending'') and that pricing amounts are excluded, which goes beyond the annotations without contradiction.

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 informative with multiple sentences but remains focused, covering the main behavior, filters, return fields, and a special status. It is not overly verbose.

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?

Given the absence of an output schema, the description compensates by listing the return fields (member_no, company name, region, etc.) and clarifying that pricing is not included. It also mentions the pending verification subcase, making it reasonably complete.

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 schema already provides descriptions for area and work. The description reinforces that these parameters are for filtering and gives examples in the schema, adding practical meaning beyond the basic type and optionality info.

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 lists verified stores (加盟店) in Yakumo Mall, and distinguishes it from siblings like find_contractor or check_named_contractor by focusing on listing all verified entries with optional filters.

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?

It explains that the tool lists verified stores and can be filtered by area (地名) and work type (工種), giving clear context. However, it does not explicitly mention when to use this over alternatives such as find_contractor or check_named_contractor.

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

All HORIZON SHIELD YAKUMO (verified contractor directory) toolsInspect
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.

Resources