Skip to main content
Glama

taxapp.nz

Rental report

get_rental_report
Read-onlyIdempotent

The rental profit and loss for one New Zealand tax year, ready for the IRD rental return (IR3R): rent and other rental income less the deductible rental expenses, per property and apportioned to each owner by their ownership share. 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_rental_report"
  }
}

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.
property_idNoOne property's report, by its id from list_properties. Leave it out for every property.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds substantive context beyond that: the report is computed per property, apportioned across owners by ownership share, and denominated in NZD. It stops short of stating permissions or behavior when multiple organisations are in scope, which the schema covers instead.

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?

A single dense sentence that front-loads the resource and its purpose, with the IR3R framing and currency note earning their place. It is readable and waste-free, though the sentence is long enough that a second shorter sentence would aid scanning.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so: income less deductible expenses, per property, apportioned by ownership share, in NZD. Nothing critical to invoking the tool is missing, though it does not describe behaviour under ambiguous multi-organisation connections.

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?

Schema description coverage is 100%, and the parameter docs are strong (tax-year naming convention, id sources, when organisation_id is required). The description adds only indirect semantics — that results split per property and per owner — which does not extend the parameters themselves. Baseline 3 is appropriate.

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 names a specific resource and scope: rental profit and loss for one New Zealand tax year, formatted for the IR3R return, broken down per property and per owner share. That is far more than a restatement of the title. It does not, however, explicitly distinguish itself from siblings like get_profit_and_loss or get_tax_summary, so an agent must infer the boundary from the 'rental' qualifier.

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?

Usage is implied rather than stated: 'ready for the IRD rental return (IR3R)' signals when this tool is the right one. But there is no explicit when-to-use versus get_profit_and_loss, get_tax_summary, or get_tax_year_overview, and no exclusions or prerequisites are given.

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.