HORIZON SHIELD KIRA

Get JCCDB Dataset Info

get_jccdb_dataset_info

Read-only

Fetch metadata, scale, license, download links, and citation for the Japan Construction Cost Database (JCCDB) to find a primary construction-cost data source.

Instructions

日本の建設費オープンデータベース(JCCDB)のメタデータ・規模・ライセンス・ダウンロードリンク・引用情報を返す。建設費の一次データ源を探している時に使う。 / Returns metadata, scale, license, download links and citation for the Japan Construction Cost Database (JCCDB), an open dataset of 526,128 records in v5.1: the item catalogue of 95,403 Japanese construction line items (43,090 verified + 52,313 extended, unchanged since v4.0) and 430,725 source-cited observations. Use when looking for a primary construction-cost data source.

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.
`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.

Changed1 schema field changedv1.0.11Oct 1, 2026

addedOutput schema / properties

Added value: +{
+  "count": {
+    "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"
+  },
+  "did_you_mean": {
+    "description": "Near matches, when an exact match was not found."
+  },
+  "lookup": {
+    "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"
+  },
+  "source_read": {
+    "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"
+  }
+}

Addedv1.0.1Aug 19, 2026

TDQS

A4.2/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 the safety profile is covered. The description adds genuinely useful non-annotation context: this is a static catalogue snapshot (v5.1, item catalogue unchanged since v4.0) with a defined record scale, which tells an agent what freshness and coverage to expect. It does not describe latency, caching, or whether the citation/download links are stable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and usage statement are front-loaded, but the content is duplicated almost wholesale in Japanese and English, which doubles length without adding information for most agents. The English half also carries dense parenthetical statistics (43,090 verified + 52,313 extended) whose relevance to tool selection is marginal.

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?

With an output schema present, the description needn't explain return values, and it correctly focuses on what the dataset is and when to reach for it. For a zero-parameter, read-only info tool this is close to complete; only the relationship to sibling cost-data tools is left unstated.

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, so the baseline is 4 and there is no parameter semantics for the description to clarify. Nothing in the description misrepresents or obscures the parameterless interface.

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 names a specific verb (returns) and a precisely scoped resource (JCCDB dataset metadata, scale, license, download links, citation), and even enumerates the concrete payload contents including record counts and version. An agent can immediately distinguish this dataset-level information tool from sibling price-query tools such as get_price_range, get_fair_price_sources, or list_cost_categories.

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?

"Use when looking for a primary construction-cost data source" gives a clear triggering context. However, it never states when NOT to use it or points to the alternative siblings (e.g., get_fair_price_sources or get_price_range) for agents that already have a source and just want prices, so routing is left partly to inference.

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

Deploy Server