au-eli-mcp

au_search_acts

Read-onlyIdempotent

Find Commonwealth Acts by searching partial titles. Enter any phrase like 'privacy' to retrieve matching Australian legislation with verifiable citations.

Instructions

Search Commonwealth Acts by (partial) title.

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": {
      "title": "<title>"
    },
    "name": "au_search_acts"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	e.g. ``"privacy"`` or ``"Aboriginal Affairs"``.

Output Schema

Name	Required	Default
`items`	No
`query`	Yes
`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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already provide comprehensive behavioral cues (read-only, idempotent, open-world). The description adds the 'partial' matching nuance but does not go into detail about matching behavior. Given the rich annotations, the description is satisfactory.

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?

The description is a single short sentence, front-loaded with the core verb and resource. No unnecessary words.

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 simple search tool with one parameter and existing output schema and annotations, the description is mostly complete. It doesn't specify result ordering or pagination, but these may be covered by the output schema.

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 covers the 'title' parameter with examples (100% coverage). The description's mention of 'partial' title adds minimal extra meaning. Baseline 3 is appropriate.

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?

The description clearly states the tool searches Commonwealth Acts by partial title, using a specific verb and resource. It distinguishes from the sibling tool 'au_get_text', which likely retrieves full text.

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 description implies usage for finding Acts by title, and the sibling tool name suggests a complementary retrieval function. However, it does not explicitly state when to use this tool versus the alternative.

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

Deploy Server