Skip to main content
Glama

HomeReady Australia rules

Get one rule

get_rule
Read-onlyIdempotent

Returns one rule by id (from list_rules): the value (duty bands, thresholds or rates), the condition it applies under, effective dates and which date decides, and links to the official sources with the dates they were read. Eligibility is decided by the revenue office.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds substance by enumerating what the returned rule contains (value, condition, effective dates, which date decides, source links with read dates) and by disclaiming any eligibility determination, which prevents the agent from misusing the result.

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 front-loaded sentence: verb and resource first, then the returned payload enumeration, then the eligibility caveat. Dense but every clause carries information; the long comma-separated list of returned fields is the only slightly unwieldy part.

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?

For a one-parameter read tool with no output schema, the description explains the return contents and provenance of the id, which is the essential missing structure. Only minors are absent, such as behavior when the id is unknown or whether the value is raw or normalized.

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 bare 'id' string has no documentation on its own. The description compensates by specifying provenance ('from list_rules'), which is the key meaning an agent needs. It does not state the id's format, but for a single opaque identifier this is largely sufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns one rule by id') and immediately ties it to the sibling that produces the id ('from list_rules'). An agent can distinguish this from the list tool without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(from list_rules)' tells the agent the id must come from the listing tool, which is real usage context. It also sets a boundary by noting eligibility is decided by the revenue office, implying this tool reports rules rather than adjudicating them. It stops short of explicit when-not-to-use guidance or handling of a non-existent id.

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