Skip to main content
Glama
Sora-bluesky

building-standards-act-mcp

by Sora-bluesky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

改正状況確認

check_law_updates
Read-onlyIdempotent

Check Japanese building law amendments via e-Gov API by law name or chapter group, with optional amendment history since a chosen date.

Instructions

法令の改正状況をe-Gov APIで確認する。法令名指定で単体チェック、グループ指定でバッチチェック、show_historyで改正履歴表示が可能。

Input Schema

NameRequiredDescriptionDefault
groupNo検証対象の章グループ（例: 1章）。省略時は全プリセットをチェック。
sinceNo基準日（YYYY-MM-DD）。この日より後に公布された改正だけを『改正あり』として報告する。省略時は今日の 12 か月前
law_nameNo法令名または略称（例: 建築基準法、建基法）。単体チェックに使用。
show_historyNotrue で改正履歴の詳細を表示。law_name 指定時のみ有効。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.11.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / since
      Added value: +{
+  "description": "基準日（YYYY-MM-DD）。この日より後に公布された改正だけを『改正あり』として報告する。省略時は今日の 12 か月前",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
  2. First observedv1.7.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds that the check is performed against the external e-Gov API, but it does not disclose rate limits, error behavior, or what output is produced.

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?

Two compact sentences with the core purpose front-loaded and the mode distinctions following. No filler, though it is very terse for a four-parameter tool.

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

Completeness3/5

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

With no output schema, the description should ideally hint at the return shape (e.g., what a '改正あり' result contains), but it does not. Annotations cover the safety profile and the schema covers parameters, leaving output format as the notable gap.

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%, so all four parameters (group, since, law_name, show_history) are already documented in the schema. The description restates the law_name/group/show_history usage but adds no syntax, format, or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (確認する) and resource (法令の改正状況), plus the mechanism (e-Gov API). It is clearly distinguishable from read-oriented siblings like get_law or search_law, though it does not explicitly name how it differs from the amendment-related sibling get_kokuji_amendments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description maps the three parameters to three usage modes (law_name=単体チェック, group=バッチチェック, show_history=履歴表示), which is useful implied guidance. However, it offers no explicit when-to-use versus siblings or any when-not/exclusion criteria.

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

Deploy Server

Other Tools