JobDoneBot

Tax Return Calc

tax-return-calc

Japan income tax and resident tax with progressive rates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`donations`	No	Donations (ふるさと納税等) in JPY
`blueReturn`	No	Blue return deduction level	none
`dependents`	No	Number of dependents
`miscRevenue`	No	Miscellaneous revenue (雑所得) in JPY
`miscExpenses`	No	Miscellaneous expenses in JPY
`lifeInsurance`	No	Life insurance premiums in JPY
`dividendAmount`	No	Dividend income in JPY
`businessRevenue`	No	Business revenue (事業収入) in JPY
`medicalExpenses`	No	Medical expenses in JPY
`socialInsurance`	No	Social insurance premiums in JPY
`businessExpenses`	No	Business expenses (事業経費) in JPY
`employmentRevenue`	No	Employment revenue (給与収入) in JPY

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed13 schema fields changedFeb 15, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / blueReturn

Added value: +{
+  "default": "none",
+  "description": "Blue return deduction level",
+  "enum": [
+    "100000",
+    "550000",
+    "650000",
+    "none"
+  ],
+  "type": "string"
+}

addedInput schema / properties / businessExpenses

Added value: +{
+  "default": 0,
+  "description": "Business expenses (事業経費) in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / businessRevenue

Added value: +{
+  "default": 0,
+  "description": "Business revenue (事業収入) in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / dependents

Added value: +{
+  "default": 0,
+  "description": "Number of dependents",
+  "maximum": 10,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / dividendAmount

Added value: +{
+  "default": 0,
+  "description": "Dividend income in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / donations

Added value: +{
+  "default": 0,
+  "description": "Donations (ふるさと納税等) in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / employmentRevenue

Added value: +{
+  "default": 0,
+  "description": "Employment revenue (給与収入) in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / lifeInsurance

Added value: +{
+  "default": 0,
+  "description": "Life insurance premiums in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / medicalExpenses

Added value: +{
+  "default": 0,
+  "description": "Medical expenses in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / miscExpenses

Added value: +{
+  "default": 0,
+  "description": "Miscellaneous expenses in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / miscRevenue

Added value: +{
+  "default": 0,
+  "description": "Miscellaneous revenue (雑所得) in JPY",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / socialInsurance

Added value: +{
+  "default": 0,
+  "description": "Social insurance premiums in JPY",
+  "minimum": 0,
+  "type": "number"
+}

First observedFeb 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only mentions 'progressive rates,' which is a calculation detail, but fails to state that this is an estimate, what the output format is, or any limitations. The description adds minimal behavioral context beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that identifies the tool's purpose and scope without waste. It is front-loaded and every word earns its place, making it appropriately sized for a high-level summary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (12 parameters, no output schema), the description is incomplete. It does not mention what the return value looks like, whether the calculation is an estimate, or how the inputs are used. This leaves the user without enough context to determine if this tool fits their needs.

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?

The input schema provides detailed descriptions for all 12 parameters with 100% coverage, so the baseline is 3. The description adds no parameter-specific semantics beyond the mention of progressive rates, which does not enhance understanding of individual inputs.

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 description clearly states it calculates Japan income tax and resident tax with progressive rates. The resource and scope are identifiable, but it doesn't distinguish itself from sibling tools like resident-tax-calc or freelance-tax-calc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description doesn't say when to use this tool versus alternatives, nor does it give prerequisites or intended use cases. It lacks any exclusions or alternative tool references.

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

All JobDoneBot tools Inspect

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

B3.1/5.0

Disambiguation2/5

Multiple tools have overlapping purposes, such as bg-remover, bg-remover-pro, pro-matting, and takumi all performing background removal, and upscaler/upscaler-pro being redundant. With 202 tools, an agent may easily select the wrong one despite detailed descriptions.

Naming Consistency4/5

Most tools use a consistent kebab-case format with descriptive names like pdf-compress, image-resizer, and tax-return-calc. Exceptions like 'takumi', 'pro-matting', and '-pro' suffixes (bg-remover-pro, upscaler-pro) are minor deviations relative to the total.

Tool Count1/5

202 tools is an extreme mismatch for an MCP server, far exceeding the typical 3-15 well-scoped range. The sheer volume makes it unwieldy for an agent to efficiently navigate and select the right tool.

Completeness4/5

The tool set provides extensive coverage across many domains, including PDF operations (20+ tools), image editing, financial calculations, e-commerce fee estimation, and YouTube utilities. Minor gaps exist in cross-tool integration, but the breadth is highly comprehensive for the apparent purpose.

Resources

Need Help?