japan-data-mcp

list_flagship_b2b_bundles

Read-onlyIdempotent

List five flagship enterprise Japanese data bundles with dataset counts, total records, JPY pricing, discounts, and B2B invoice availability. Use for bulk ZIP packages or B2B purchasing.

Instructions

List the 5 Flagship Enterprise All-in-One Data Bundles (BUNDLE-01 Real Estate, BUNDLE-02 Government Procurement, BUNDLE-03 Healthcare, BUNDLE-04 Renewable Energy/GX, BUNDLE-05 Municipal Finance/Resilience) with included dataset counts, total records, JPY pricing, discount rates, and qualified B2B invoice availability. WHEN TO USE: Use only when the user asks about bulk downloadable ZIP packages, enterprise pricing, or B2B invoice options. WHEN NOT TO USE: Do not use for listing individual API datasets (use 'list_japan_datasets') or querying actual data records (use 'search_japan_official_data').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bundle_code`	No	Optional exact bundle identifier from 'BUNDLE-01' to 'BUNDLE-05' (case-insensitive). If omitted, returns all 5 flagship bundles.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	No	Number of flagship bundles returned.
`bundles`	No	List of bundle metadata objects with bundle_code, title, datasets_included, records, and price_jpy.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.4Oct 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / bundle_code / description

Previous value: -"Optional bundle code filter (e.g., 'BUNDLE-01' through 'BUNDLE-05')."New value: +"Optional exact bundle identifier from 'BUNDLE-01' to 'BUNDLE-05' (case-insensitive). If omitted, returns all 5 flagship bundles."

addedOutput schema / properties / bundles / description

Added value: +"List of bundle metadata objects with bundle_code, title, datasets_included, records, and price_jpy."

addedOutput schema / properties / total / description

Added value: +"Number of flagship bundles returned."

Changed1 schema field changedv1.0.2Oct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "bundles": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Oct 15, 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, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real context by disclosing the bounded result set (exactly 5 bundles) and the field content returned (dataset counts, total records, JPY pricing, discount rates, B2B invoice availability). It omits pagination/rate-limit behavior, but the bounded cardinality removes most ambiguity.

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 opening sentence is front-loaded with the core scope, and the WHEN TO USE / WHEN NOT TO USE blocks are tightly structured and immediately scannable. The inline enumeration of all five bundle names is somewhat verbose, but it doubles as valid-value disambiguation rather than filler.

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?

For a one-parameter, read-only list tool with an output schema present, the description need not explain return structure. Between the scope statement, the usage routing, and the annotated safety profile, an agent has everything required to select and invoke it correctly.

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% and the single optional bundle_code parameter is fully documented in the schema, including the BUNDLE-01..BUNDLE-05 range and case-insensitivity. The description's enumeration of the five bundles reinforces the valid values but adds no syntax or semantics beyond what the schema already provides, so baseline 3 applies.

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 ('List the 5 Flagship Enterprise All-in-One Data Bundles') and enumerates the exact bundle codes and names, so an agent knows precisely what comes back. It also explicitly names the sibling tools it is not (list_japan_datasets, search_japan_official_data), making it trivially distinguishable from them.

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?

Contains explicit WHEN TO USE ('bulk downloadable ZIP packages, enterprise pricing, or B2B invoice options') and WHEN NOT TO USE clauses that route the agent to two named alternatives with their respective conditions. Nothing about selection is left 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