---
name: tax-jobs
description: "Step-by-step job recipes for the Tax Numbers MCP server: Look up US federal tax figures; Check VAT or sales tax registration duty; Look up the IRS mileage rate. Use when the user asks things like \"What is the standard deduction for a single filer in 2026?\" or \"I run a German shop that sells e-books. I made 14,000 EUR from buyers in France this year. Do I have to register for VAT, and at what rate?\""
license: MIT
---

# Tax Numbers jobs

Each section below walks through one job with the tools of the `tax` MCP server. The same recipes are MCP prompts (prompts/list) on `https://api.openkrill.app/gateway/mcp`.
Connect the server at `https://tax.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Look up US federal tax figures

Job: Look up US federal tax figures, with the Tax Numbers MCP server.

Use the `get_tax_parameters` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "What is the standard deduction for a single filer in 2026?"

Steps:
1. Call `get_tax_parameters` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `year`, `topic`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"year":2025,"topic":"standard_deduction","filing_status":"single"}`
4. For the request "What is the standard deduction for a single filer in 2026?", a correct answer looks like this: status current; a row Standard deduction of 16,100 dollars for single, with its source Rev. Proc. 2025-32 section 4.14(1) and the URL of the Revenue Procedure; last_verified is present.
5. Follow the server's own rules:
   - Use get_tax_parameters for published federal figures (brackets, standard deduction, capital gains thresholds, self-employment tax, retirement limits, mileage) and quote the figure with its source document.
   - Never use remembered figures: tax numbers change yearly, so always call a tool.
   - Ask for the tax year and filing status if the user did not give them; never guess them.
   - If a result has status unsupported_year or not_available, tell the user which years are available and do not substitute another year.
   - Status amended means a figure changed after first release; mention it when it matters.
   - With every estimate, say it is an estimate and not tax advice, and say what the not_included list leaves out.
   - Quote must_register, the threshold, the rate and the filing rhythm with the source link and its checked date, and always repeat the not_tax_advice line.
   - If status is not_covered, show the covered places; if must_register is unclear, say what is unclear and suggest an accountant.
   - If stale_data is true, say the table is overdue for a check.
   - Never fill a gap from memory.
   - The other tools cover US federal income tax only: they do not cover state income tax, file or prepare a return, or advise on what the user should do.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `get_tax_parameters`).

## Check VAT or sales tax registration duty

Job: Check VAT or sales tax registration duty, with the Tax Numbers MCP server.

Use the `tax_duty` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "I run a German shop that sells e-books. I made 14,000 EUR from buyers in France this year. Do I have to register for VAT, and at what rate?"

Steps:
1. Call `tax_duty` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `seller_country`, `buyer_place`, `product_kind`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"seller_country":"DE","buyer_place":"FR","product_kind":"digital_products","yearly_sales":14000}`
4. For the request "I run a German shop that sells e-books. I made 14,000 EUR from buyers in France this year. Do I have to register for VAT, and at what rate?", a correct answer looks like this: status ok; must_register yes because 14,000 EUR is over the 10,000 EUR One Stop Shop limit; rate 20 percent standard for France; a quarterly return due at the end of the month after the quarter; sources linking the European Commission One Stop Shop and the Taxes in Europe Database with the day each was checked; the not tax advice line.
5. Follow the server's own rules:
   - Never use remembered figures: tax numbers change yearly, so always call a tool.
   - Ask for the tax year and filing status if the user did not give them; never guess them.
   - If a result has status unsupported_year or not_available, tell the user which years are available and do not substitute another year.
   - Status amended means a figure changed after first release; mention it when it matters.
   - With every estimate, say it is an estimate and not tax advice, and say what the not_included list leaves out.
   - Use tax_duty when a seller asks whether to register for VAT or sales tax in an EU country, the United Kingdom or a US state: pass seller_country, buyer_place (write a US state as US-TX; a bare CA means Canada), product_kind and yearly_sales in the buyer place's currency (leave it out when the user gave no figure, never send 0).
   - Quote must_register, the threshold, the rate and the filing rhythm with the source link and its checked date, and always repeat the not_tax_advice line.
   - If status is not_covered, show the covered places; if must_register is unclear, say what is unclear and suggest an accountant.
   - If stale_data is true, say the table is overdue for a check.
   - Never fill a gap from memory.
   - The other tools cover US federal income tax only: they do not cover state income tax, file or prepare a return, or advise on what the user should do.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `tax_duty`).

## Look up the IRS mileage rate

Job: Look up the IRS mileage rate, with the Tax Numbers MCP server.

Use the `get_mileage_rate` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "What was the IRS business mileage rate on 15 March 2026, and what is it for medical driving?"

Steps:
1. Call `get_mileage_rate` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `date`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"date":"2026-03-15"}`
4. For the request "What was the IRS business mileage rate on 15 March 2026, and what is it for medical driving?", a correct answer looks like this: status ok; business 72.5 cents per mile, medical 20.5, charity 14, period 2026-01-01 to 2026-06-30 and notice IR-2025-128 (the rates changed on 1 July 2026).
5. Follow the server's own rules:
   - Use get_mileage_rate for the standard mileage rate on a date, tax_deadlines for filing and estimated-payment dates, and estimate_federal_tax for a rough federal figure.
   - Never use remembered figures: tax numbers change yearly, so always call a tool.
   - Ask for the tax year and filing status if the user did not give them; never guess them.
   - If a result has status unsupported_year or not_available, tell the user which years are available and do not substitute another year.
   - Status amended means a figure changed after first release; mention it when it matters.
   - With every estimate, say it is an estimate and not tax advice, and say what the not_included list leaves out.
   - Quote must_register, the threshold, the rate and the filing rhythm with the source link and its checked date, and always repeat the not_tax_advice line.
   - If status is not_covered, show the covered places; if must_register is unclear, say what is unclear and suggest an accountant.
   - If stale_data is true, say the table is overdue for a check.
   - Never fill a gap from memory.
   - The other tools cover US federal income tax only: they do not cover state income tax, file or prepare a return, or advise on what the user should do.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `get_mileage_rate`).