Skip to main content
Glama

jimu (renamed to Tax Compass)

支払期日の計算(取適法の60日・締め日と支払日)

jp_payment_due_date
Read-onlyIdempotent

Compute payment-term dates under Japan's 中小受託取引適正化法 (取適法, in force from 2026-01-01, formerly the 下請法) Article 3, using the JFTC text: the 60th day counted with the receipt date as day 1, the deemed due dates (receipt date if no due date was set; the 60th day if it was set later), and for an agreed due date or a monthly cut-off rule (締め日・支払月・支払日) the payment date, its day number and whether it is within 60 days. For a monthly rule only (the two-month treatment applies to monthly cut-off rules, not to an agreed due date) it also gives the last day of the JFTC's two-month treatment (受領後2か月以内) and whether the payment is within it, and whether the payment date is a bank holiday and the postponement fits the JFTC's conditions. Special cut-off rules for continuously provided services are not covered. It does not decide whether the act applies to a transaction. Dates must be within the holiday data (currently up to 2027-12-31).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "received_on": "<received_on>"
    },
    "name": "jp_payment_due_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthlyNo月単位の締切制度(例:末日締め翌月末日払い=cutoff_day "end"・pay_month_offset 1・pay_day "end")
received_onYes給付を受領した日(役務は提供を受けた日。日数がかかる役務は終わった日)YYYY-MM-DD
agreed_due_dateNo決めた支払期日(YYYY-MM-DD)。monthly と一緒には使わない

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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: the legal version and effective date (2026-01-01, formerly 下請法), the supported date horizon of 2027-12-31, and the scope limits. It does not describe failure modes, e.g. what happens when a date falls outside the holiday data or when agreed_due_date and monthly are both supplied.

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?

Every sentence carries substantive information and the core rule is front-loaded in the first clause. The weakness is structural: it is one dense run-on paragraph with nested parentheticals and re-states the 60th-day rule in two places, which makes it harder to scan than a short bulleted breakdown would be.

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?

The tool is moderately complex (three params, one nested object, statutory branch logic) but an output schema exists, so return values need no explanation. The description covers both input modes, the legal basis, the date horizon and the out-of-scope areas. Minor gap: it does not state behavior when both mutually exclusive inputs are provided or when received_on is outside the supported holiday range.

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 baseline is 3, but the description genuinely adds meaning: it explains that the two-month treatment applies to monthly cut-off rules but not to an agreed due date, and that holiday postponement is evaluated for the monthly path. It also clarifies that the receipt date is day 1, which is the semantic crux of received_on. It does not restate the cutoff_day/pay_day/pay_month_offset encoding, but the schema already does that.

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 computation (payment-term dates under 取適法 Article 3), the exact statutory rule it implements (60th day counted with receipt date as day 1), and the concrete outputs (deemed due date, payment date, day number, within-60-days flag, two-month treatment, holiday postponement). That is enough for an agent to distinguish it from the date-arithmetic siblings like jp_add_business_days or jp_holidays without opening the schema.

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 gives clear positive triggers (agreed due date or a monthly cut-off rule) and explicit exclusions: it does not decide whether the act applies, it does not cover special cut-off rules for continuously provided services, and dates must fall within the holiday data (currently to 2027-12-31). What it lacks is an explicit pointer to an alternative tool when those exclusions bite, so it stops short of full when/when-not/alternative routing.

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