Japan CAA Commercial Transactions Actions

Japanese CAA commercial transactions actions (by company)

caa_action_lookup

Read-only

Has the Japanese Consumer Affairs Agency published a national action under the Act on Specified Commercial Transactions against a company with this name? Give the name in Japanese and optionally the head office prefecture and municipality. Returns action date, types, articles, head office, suspension period, source URL, retrieved_at, page SHA-256. Status found, not_found_in_checked_records (with checked_scope) or unknown. Matched by name and location only.

Input Schema

Name	Required	Description
`name`	Yes	Company name in Japanese, e.g. 株式会社HOPE Group (full/half width, spaces and the position of 株式会社 are normalized)
`prefecture`	No	Optional head office prefecture in Japanese or English (東京都, Tokyo, 大阪府, Osaka)
`municipality`	No	Optional head office municipality or ward in Japanese (新宿区, 大阪市, 仙台市泉区)

Output Schema

Name	Required	Description
`query`	Yes
`terms`	Yes	URL of the terms of service.
`source`	Yes	Where the answer comes from: the CAA enforcement list and when this service last read it.
`status`	Yes	found = a respondent with this normalized name (and location, when given) is on the CAA list; not_found_in_checked_records = none in the action pages read (see checked_scope); unknown = list not loaded or stale, pages that may concern this name not read yet or unreadable, or location not published (unknown_reason). A status other than found is not evidence that no action exists.
`records`	Yes
`provenance`	Yes	Freshness receipts for every upstream source used.
`answered_at`	Yes
`attribution`	Yes
`not_covered`	Yes
`status_note`	Yes
`legal_notice`	Yes
`checked_scope`	Yes	What was checked: national actions under the Act on Specified Commercial Transactions on the CAA list, the fiscal years covered and the time of the list read.
`similar_names`	Yes	Respondents whose normalized name contains the query. Not matches.
`official_check`	Yes	Read first: actions as published by the CAA at retrieved_at, matched by name and location only; check the official action page.
`unknown_reason`	Yes
`registry_status`	Yes
`same_name_other_location`	Yes	Records with this name whose published head office does not match the location given. They may be different companies.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only and open-world safety, yet the description adds real behavioral context: the three possible statuses including 'not_found_in_checked_records (with checked_scope)' and 'unknown', plus the explicit caveat that matching is by name and location alone. This discloses the false-negative risk an agent needs for interpretation, though provenance handling (SHA-256, retrieved_at) is only named, not explained.

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?

Front-loaded with the core question, then inputs, then return fields, then status vocabulary — a logical order with essentially no filler. The return-field enumeration is somewhat list-heavy and partially redundant with the output schema, but it is compact.

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?

For a read-only, single-entity lookup with a full schema and an output schema, the description covers purpose, inputs, matching limits, and status outcomes. Enumerating return fields overlaps with the output schema, and the meaning of 'unknown' versus the not-found status could be spelled out further.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds that all three parameters are purely match keys ('matched by name and location only') and that the name must be Japanese. That framing gives the parameters meaning beyond their individual schema descriptions.

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 opens with a precise, answerable question — whether the CAA published a national action under the Act on Specified Commercial Transactions against a company with a given name. The verb/resource pair is specific and the singular 'lookup by company' framing distinguishes it from the sibling caa_action_list.

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 clearly states the input precondition (Japanese company name, optionally head office prefecture/municipality) and the matching constraint ('matched by name and location only'), which tells the agent when this tool will not find a record. It stops short of explicitly contrasting with caa_action_list, leaving that routing to inference from the names.

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

All Japan CAA Commercial Transactions Actions 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?