Skip to main content
Glama

taxapp.nz

Tax summary

get_tax_summary
Read-onlyIdempotent

A person's tax summary for one New Zealand tax year: their commission (with the GST in it), their share of the long-term rent received, their share of short-stay income (shortStay, apart from the rent: what guests paid, the GST in it and the income without it), and taxapp's indicative income tax and independent earner tax credit (IETC), worked out from that year's IRD rates by stepping through the tax brackets (their PAYE salary first, then commission, then rent, then short stays), with each source's income and tax and the combined total; totals.gst is the commission's GST plus their own GST on short stays; the employer deducts the tax on the salary, so it is not in the tax payable. The commission's ACC levy is set out as ACC's invoice (commission.accLevyInvoices); it is not income tax. No expenses are deducted. Without a contractor it is the whole organisation's: each person's tax on their own income, added up. These are planning figures to help the person file, not an IRD assessment. Money is in NZD.

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": "get_tax_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearNoThe New Zealand tax year, named by the year it ends in: 2026 is 1 April 2025 to 31 March 2026. Leave it out for the current tax year.
organisation_idNoThe id of the organisation to use, from list_organisations. Leave it out when the connection covers only one organisation; it is required when it covers more than one.
contractor_contact_idNoWhose summary: a contractor's contact id, from list_contacts (contact type contractor). Leave it out when the organisation has only one contractor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond them: the calculation order through tax brackets, GST treatment, exclusion of expenses, treatment of PAYE salary tax, the fact that the ACC levy is not income tax, and the caveat that these are planning figures rather than an IRD assessment.

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 description is front-loaded with its purpose and every clause carries some substantive information, but the first sentence is an extremely dense run-on covering many output fields. It is functional but hard to scan, and could be structured more cleanly.

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

Completeness5/5

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

Given that there is no output schema, the description does the necessary work of explaining what the summary contains, how it is calculated, what is included or excluded, and what currency the figures are in. An agent has enough information to call it and interpret its output correctly.

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 description coverage is 100%, so the baseline would be 3, but the description adds meaningful semantics for omitting contractor_contact_id: without a contractor it returns the whole organisation's tax, with each person's tax on their own income added up. That is more than the schema itself conveys about the omission behavior.

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 states a specific verb and resource: a person's tax summary for one New Zealand tax year, then breaks down the components (commission, rent share, short-stay income, indicative income tax, IETC). It does not explicitly distinguish this from the sibling get_tax_year_overview, so it stops short of a 5.

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 useful context that these are planning figures to help the person file, not an IRD assessment, and explains that omitting a contractor produces an organisation-wide aggregate. However, it does not say when to use this versus get_tax_year_overview or other income/tax reporting siblings, nor does it give explicit exclusions.

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.