Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

list_rules

List the tax rules the calculators use (ids, values, ATO/IRD/Employment NZ source URLs and the date each was last checked). Optionally filter by jurisdiction (AU or NZ) or topic (tax, mls, fbt, holidays).

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

Input Schema

NameRequiredDescriptionDefault
topicNo
jurisdictionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden: 'List' plus the described payload imply a safe, non-mutating read that returns ATO/IRD/Employment NZ source URLs and check dates. It does not mention pagination, result size, or whether topic matching is exact or fuzzy — moderate gaps for a zero-annotation tool but the read-only nature is clear.

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?

Two sentences, zero filler, with the core purpose and return contents front-loaded before the optional-filter sentence.

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 and no annotations, the description covers purpose, payload shape, and both parameters adequately for a simple two-parameter list tool; only filter-combination and matching behavior are left unstated.

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 0%, so the description must compensate; it does so by naming both parameters and, importantly, spelling out the allowed jurisdiction values (AU/NZ, matching the enum) and the topic domain (tax, mls, fbt, holidays), which the schema leaves as an unconstrained string. It stops short of saying whether the two filters are ANDed.

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?

Opens with a specific verb+resource ('List the tax rules the calculators use') and enumerates the returned fields (ids, values, source URLs, last-checked dates), which clearly separates it from the singular get_rule sibling.

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?

States that filtering is optional and names the two filter axes, which implies 'call with no arguments to get everything', but never says when to prefer a filtered call, when to use get_rule instead, or whether filters combine.

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