au-eli-mcp

au_get_text

Read-onlyIdempotent

Retrieve the current consolidated text of an Australian Act using its FRLI identifier for verifiable legal citations.

Instructions

Fetch the current consolidated text of an Act by its FRLI identifier.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`frli_id`	Yes	e.g. ``"C2004A00042"``.

Output Schema

TableJSON Schema

Name	Required	Default
`title`	No
`content`	No
`eli_uri`	No
`frli_id`	Yes
`eli_note`	No	Australia has not deployed ELI. eli_uri is the durable legislation.gov.au document URL (https://www.legislation.gov.au/{frli_id}/latest), keyed on the Federal Register of Legislation's own persistent identifier (FRLI ID) - never invented.
`byte_size`	No
`truncated`	No
`source_url`	No
`dataset_note`	No	The Federal Register of Legislation (legislation.gov.au) is Australia's official source of Commonwealth legislation. Australia has no ELI scheme; eli_uri carries the durable legislation.gov.au URL keyed on the document's own FRLI identifier (see eli_note). Discover by title (au_search_acts), then fetch the current consolidated text by frli_id. This MVP covers Acts only; regulations and other instrument types are not yet covered.
`human_readable_citation`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so description does not need to repeat safety traits. However, description adds no detail about response format, error handling, or what constitutes 'current consolidated text'. Without annotations, this would score lower.

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?

One sentence, no fluff. All necessary information is front-loaded. Every word serves a purpose.

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?

Given the tool's simplicity, one parameter, and the presence of an output schema (not shown but indicated), the description is sufficient. It could mention the output type explicitly, but the schema covers that.

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?

The input schema has 100% description coverage for the single parameter 'frli_id' with an example. The description does not add further semantic context beyond what the schema already provides.

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?

Clearly states the action ('Fetch'), resource ('current consolidated text of an Act'), and identifier type ('FRLI identifier'). Distinguishes from sibling tool 'au_search_acts' which searches acts rather than retrieves text.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Does not mention prerequisite of having an FRLI identifier, nor refer to the sibling tool for searching. The description implies usage but provides no explicit context for decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server