Skip to main content
Glama

jimu (renamed to Tax Compass)

個人事業主の届け出・申告・納付の期限の目安

jp_filing_deadlines
Read-onlyIdempotent

List the usual deadlines for a sole proprietor in Japan for one year, from National Tax Agency pages: the opening notice (開業届, due by the income-tax return deadline of the opening year), the blue-return application (青色申告承認申請: March 15, or within 2 months of opening when the business started on or after January 16), the income-tax return (March 15 of the next year), the consumption-tax return for individuals (March 31), the two estimated-tax installments (予定納税: July 31, November 30) and the special withholding-tax payment dates (納期の特例: July 10, January 20). Each date is moved to the next day when it falls on a weekend, national holiday, December 29–31 or January 1–3 (国税通則法 第10条第2項). Give the year and/or the opening date; each item says when it applies, and the caller decides which apply. For a business opened before 2026-01-01 the opening-notice deadline is not given (the article changed on that day). Years are accepted up to one year before the end of the holiday data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jp_filing_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo何年分か(西暦・今は 2026 年分まで)。省くと開業の日の年
business_start_dateNo開業の日(YYYY-MM-DD)。入れると開業届・青色申告承認申請の期限も出す

Output Schema

NameRequiredDescriptionDefault
notesYesこの答えに効いた決まり・前提(日本語)
resultYes
doc_urlYes人が読む説明のページ(式・出所・例)。利用者に次に読んでもらう先
sourcesYes
law_as_ofNo出所が書く法令の基準日(例:2026-04-01=令和8年4月1日現在法令等)
checked_onYesCyclix Agents が出所を最後に確かめた日
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. Beyond that, the description discloses the data source (National Tax Agency pages), the weekend/holiday/Dec 29–Jan 3 rollover rule with its legal basis (国税通則法 第10条第2項), and two real caveats: the opening-notice deadline is omitted for businesses opened before 2026-01-01, and years are limited to one year before the end of the holiday data. These are genuine behavioral disclosures an agent could not infer from the schema.

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 opening clause is well front-loaded, but the body is one dense run-on paragraph whose long parentheticals (with Japanese terms, specific dates and a statute citation) are hard to scan. Every element is substantive, yet the content would be far more usable split into a short purpose statement followed by a bulleted list of covered deadlines and caveats.

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?

An output schema exists, so return values need no explanation, and for a two-optional-parameter lookup the description covers source, scope, rollover semantics and edge cases well. The only meaningful gap is that it does not tell the agent what the sibling tools cover, so routing between this and jp_payment_due_date / jp_holidays is left to inference.

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; the description earns above that by giving operational meaning to the parameters — the opening date drives whether the 開業届 and 青色申告承認申請 deadlines appear, and the accepted-year window is stated. It does not add much about defaulting behavior for `year` beyond what the schema's own description says (省略すると開業の日の年).

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 and resource (list the usual deadlines for a sole proprietor in Japan over one year) and then enumerates the exact items returned: the opening notice, blue-return application, income-tax return, consumption-tax return, estimated-tax installments and special withholding dates. It is distinguishable from sibling date tools such as jp_payment_due_date or jp_business_days_between because it produces a fixed calendar of statutory filing deadlines rather than doing arithmetic.

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?

It gives input-oriented guidance ('Give the year and/or the opening date; each item says when it applies, and the caller decides which apply'), which tells the agent the tool is a reference lookup rather than a filter. However, it never states when to prefer this tool over the date-arithmetic siblings, nor any exclusion such as entity types covered (sole proprietors only, not corporations).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources