Japan Agent API

Japan municipality batch lookup (paid)

jp_municipality_batch

Read-only

Which codes are valid on a date for up to 50 Japanese municipalities? e-Stat LOD change history (CC BY 4.0): status mapped / split_candidates (all successors, not apportioned) / unknown / invalid, the code valid on as_of with English and Japanese names, change type and date, confirmed JMA warning areas only, and J-LIS convenience-store certificate availability (available / not_listed / unknown). Facts only; no document preparation or legal advice. Retrying with the same payment is not charged.

Input Schema

Name	Required	Description	Default
`as_of`	No	Default as_of for items that do not set their own.
`items`	Yes	1 to 50 lookups; each gives code, or prefecture and name.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "checked_scope": {
+          "type": "string"
+        },
+        "count": {
+          "type": "number"
+        },
+        "disclaimer": {
+          "type": "string"
+        },
+        "license_note": {
+          "type": "string"
+        },
+        "national_rules": {},
+        "out_of_scope": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "provenance": {
+          "description": "Freshness receipts for every upstream source used.",
+          "items": {
+            "additionalProperties": {},
+            "description": "Freshness receipt for one upstream source.",
+            "properties": {
+              "content_sha256": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "fetch_status": {
+                "description": "found / empty / stale / unavailable / unsupported (see catalog fetch_status_values).",
+                "enum": [
+                  "found",
+                  "empty",
+                  "stale",
+                  "unavailable",
+                  "unsupported"
+                ],
+                "type": "string"
+              },
+              "parser_version": {
+                "type": "string"
+              },
+              "processed_by": {
+                "type": "string"
+              },
+              "retrieved_at": {
+                "description": "When this service retrieved the upstream data (null if unknown).",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "source": {
+                "additionalProperties": {},
+                "description": "Publisher and URL of the upstream document or dataset.",
+                "properties": {
+                  "publisher": {
+                    "type": "string"
+                  },
+                  "url": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "publisher",
+                  "url"
+                ],
+                "type": "object"
+              },
+              "upstream_updated_at": {
+                "description": "Update time stated by the upstream, or null when it states none.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "source",
+              "upstream_updated_at",
+              "retrieved_at",
+              "content_sha256",
+              "parser_version",
+              "fetch_status",
+              "processed_by"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "receipt_id": {
+          "description": "Receipt id of the settled paid call (\"rcpt_\" + 64 hex). Use with get_receipt.",
+          "type": "string"
+        },
+        "responded_at": {
+          "type": "string"
+        },
+        "results": {
+          "description": "One result per item, in input order.",
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "as_of": {
+                "type": "string"
+              },
+              "as_of_codes": {
+                "description": "Codes valid on as_of, with names, JMA area and J-LIS certificate availability.",
+                "items": {
+                  "additionalProperties": {},
+                  "properties": {
+                    "code": {
+                      "type": "string"
+                    },
+                    "convenience_store_certificates": {
+                      "additionalProperties": {},
+                      "properties": {
+                        "status": {
+                          "type": "string"
+                        }
+                      },
+                      "required": [
+                        "status"
+                      ],
+                      "type": "object"
+                    },
+                    "jma_area": {
+                      "additionalProperties": {},
+                      "properties": {},
+                      "type": "object"
+                    }
+                  },
+                  "required": [
+                    "code",
+                    "jma_area",
+                    "convenience_store_certificates"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "changes": {
+                "items": {
+                  "additionalProperties": {},
+                  "properties": {},
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "input": {
+                "additionalProperties": {},
+                "description": "The query as understood (code or prefecture and name, and as_of).",
+                "properties": {
+                  "as_of": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "as_of"
+                ],
+                "type": "object"
+              },
+              "status": {
+                "description": "mapped / split_candidates / unknown / invalid.",
+                "enum": [
+                  "mapped",
+                  "split_candidates",
+                  "unknown",
+                  "invalid"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "input",
+              "status",
+              "as_of",
+              "as_of_codes",
+              "changes"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "retrieved_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "source": {
+          "type": "string"
+        },
+        "status_values": {
+          "additionalProperties": {
+            "type": "string"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "summary": {
+          "additionalProperties": {},
+          "properties": {
+            "invalid": {
+              "type": "number"
+            },
+            "mapped": {
+              "type": "number"
+            },
+            "split_candidates": {
+              "type": "number"
+            },
+            "unknown": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "mapped",
+            "split_candidates",
+            "unknown",
+            "invalid"
+          ],
+          "type": "object"
+        },
+        "terms": {
+          "description": "URL of the terms of service.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "receipt_id",
+        "count",
+        "summary",
+        "results",
+        "national_rules",
+        "out_of_scope",
+        "status_values",
+        "disclaimer",
+        "checked_scope",
+        "source",
+        "license_note",
+        "provenance",
+        "retrieved_at",
+        "responded_at",
+        "terms"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": {},
+      "description": "x402 PaymentRequired (returned with isError true when payment is required or was not accepted).",
+      "properties": {
+        "accepts": {
+          "description": "Payment options (x402 v2 PaymentRequirements).",
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "network": {
+                "type": "string"
+              },
+              "scheme": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "scheme",
+              "network"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "additionalProperties": {},
+          "properties": {
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "url"
+          ],
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ],
+      "type": "object"
+    }
+  ],
+  "description": "Either the paid result (with receipt_id) or, with isError true, the x402 PaymentRequired to pay and retry.",
+  "properties": {},
+  "type": "object"
+}

First observedOct 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond them: the tool is paid and 'Retrying with the same payment is not charged' (retry/idempotency behavior), plus the data provenance (e-Stat LOD, CC BY 4.0) and status taxonomy returned.

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 key question is front-loaded, which is good, but the second half is a dense run-on enumerating status values, name languages, change fields, and certificate availability. It is informative yet cluttered rather than tight.

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, return values need not be explained, and the batch item rules live in the schema. The description still covers payment/retry behavior and data licensing, leaving little an agent needs missing, though the single-vs-batch routing is not spelled out.

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 code, name, prefecture, and as_of are fully documented in the schema. The description adds little parameter-level detail (only that answers are 'valid on as_of'), so the baseline 3 applies.

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?

The opening question names the verb (validate/lookup) and resource (Japanese municipality codes on a date) and the batch scope ('up to 50'), and the field list makes the output concrete. It distinguishes itself from the sibling jp_municipality only implicitly via the 50-item cap, never naming the single-lookup alternative.

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?

Usage is only implied: 'up to 50' signals when to prefer batch over a single lookup, and 'Facts only; no document preparation or legal advice' sets a scope boundary. There is no explicit when-to-use/when-not statement nor a named alternative, so the agent must infer the routing from the item limit.

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

All Japan Agent API tools Inspect

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

Need Help?