Skip to main content
Glama

jp-crypto-tax-rules

by io.github.kodandy

List structured Japanese crypto tax rules

list_tax_rules

FREE — returns structured rules. Catalog of machine-readable Japanese crypto-asset tax rules (rules-as-code): titles, status (current / enacted_pending), effective dates and statutory citations, filterable by category, taxpayer and tax_year. tax_year resolves the current-vs-2028-reform epoch per rule (applies / pending_enforcement). Sources are public only (NTA FAQ, e-Gov statutes, MOF documents); not tax advice. 一般的な税制情報の提供であり、個別の税務判断は税理士にご相談ください。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoCategory filter: corporate | cost_basis | filing | income_classification | reform_2028 | taxable_events
tax_yearNoTax year to resolve rule applicability, e.g. 2026 or 2028
taxpayerNoTaxpayer filter: all | corporate | individual

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided. The description notes 'FREE — returns structured rules' and disclaims tax advice, but does not explicitly state read-only behavior, authorization needs, or rate limits. As a list operation, read-only is implied but not confirmed.

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 description is front-loaded with 'FREE — returns structured rules' and key details, but includes a Japanese disclaimer that adds length. Overall, it is clear and concise without excess.

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?

Given no output schema and no annotations, the description covers return fields (titles, status, dates, citations), filtering options, and source types. Lacks details on pagination or response size, but sufficient for basic usage.

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% with basic descriptions. The description adds value by explaining that tax_year 'resolves the current-vs-2028-reform epoch per rule (applies / pending_enforcement)', and lists category filter values, enhancing understanding beyond the schema.

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 title 'List structured Japanese crypto tax rules' and description clearly state it returns a catalog of machine-readable rules with fields like titles, status, dates, citations. The description differentiates from siblings (get_rule_pack, get_tax_parameters, get_tax_rule) by being a list/filter operation.

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 implies usage via filtering parameters but does not explicitly state when to use this tool versus sibling tools (e.g., for listing vs. single rule retrieval). No 'when not to use' guidance is provided.

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

All jp-crypto-tax-rules toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: list_tax_rules catalogs rules, get_tax_rule retrieves a single rule, get_tax_parameters provides tax parameters, and get_rule_pack delivers scenario-based bundles. No functional overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: list_tax_rules, get_tax_rule, get_tax_parameters, get_rule_pack. The naming convention is uniform and predictable.

Tool Count5/5

With 4 tools, the server is well-scoped for its domain (Japanese crypto tax rules). Each tool serves a necessary function, and the count is neither too sparse nor excessive.

Completeness4/5

The tool surface covers cataloging, single-rule retrieval, parameters, and scenario packs. Minor gap: no batch retrieval for full rules by category, but list with filtering partially addresses this.

Resources