Skip to main content
Glama

HomeReady Australia rules

List Australian property duty rules

list_rules
Read-onlyIdempotent

Lists HomeReady's checked rules for Australian stamp (transfer) duty scales, first home buyer exemptions and concessions, and foreign buyer surcharges, by state or territory. Returns each rule's id, title, status and the date its sources were last checked, with the rules file version and terms. General information only.

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
topicNoOptional topic filter
jurisdictionNo

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 cover readOnly, idempotent, non-destructive, closed-world behavior, and the description adds real value beyond them: it enumerates the returned fields (id, title, status, sources-last-checked date, rules file version and terms) and carries a 'General information only' disclaimer signaling this is not advice. It omits pagination/result-size behavior, which keeps it from a 5.

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?

Two sentences, front-loaded with what is listed before what is returned. The closing 'General information only' disclaimer is short and earns its place as a safety signal, though the return-field enumeration is dense.

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?

A simple read-only list tool with full annotation coverage and no output schema, so the description's return-field summary plus disclaimer makes it callable without further guesswork. Only the absence of any result-size or ordering note leaves a small gap.

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 coverage is 50% — topic has its own description ('Optional topic filter') while jurisdiction has none. The description partially compensates by naming the topic categories that map to the enum values and by saying rules are organized 'by state or territory', but it never states that both parameters are optional filters or how they combine.

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?

States a specific verb (Lists) and resource (checked rules for stamp duty scales, first home buyer exemptions/concessions, foreign buyer surcharges) scoped by state/territory. It does not explicitly differentiate itself from the sibling get_rule, leaving the list-vs-single-record distinction implicit.

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 through 'by state or territory' and the topic/jurisdiction filters, but the description never says when to list versus when to fetch a single rule via get_rule, and gives no exclusions or prerequisites.

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