ABS Data (observed)

Search ABS tables

search_tables

Read-onlyIdempotent

Find ABS statistical tables (dataflows) by topic words, geography level or frequency. Matches table names, topics and dimension names, and also option labels inside dimensions — a search for 'rent' finds CPI through its INDEX option 'Rents' and reports the match in matchedOptions. Census tables published at several geography levels are collapsed to one result with familyGeographies listing the others (use the geography filter to pick one). Every result has data. When the person describes a situation rather than a dataset, search for each thing it depends on (prices, wages, rents, population...). Start here, then describe_table.

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

Input Schema

Name	Required	Description
`limit`	No
`query`	No	Free text over ids, names, topics, dimensions
`frequency`	No	A annual, S semi-annual, Q quarterly, M monthly, W weekly, D daily
`geography`	No	Restrict to a geography level, e.g. SA2, LGA

Output Schema

Name	Required	Description	Default
`total`	Yes
`results`	Yes
`provenance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is free. The description still adds genuinely non-obvious behavior: option-label matching inside dimensions with the match surfaced in matchedOptions, and geography-family collapsing with familyGeographies. It stops short of noting the result cap (limit max 50) or result ordering, which matters for a search tool.

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?

Front-loaded with the core purpose, then behavior, then the 'start here' workflow cue — a sensible order. It is dense but nearly every clause carries information; only the parenthetical example ('rent' finds CPI) borders on elaboration rather than instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema handling return values and annotations covering safety, the description supplies exactly the missing layer: how matching works, how duplicates are collapsed, the guarantee that results have data, and where to go next. Nothing an agent needs to call this correctly is absent.

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 75%, so baseline is already 3. The description adds real meaning beyond the schema: it explains that matching spans ids, names, topics, dimension names and option labels, and that the geography parameter is the lever for choosing among collapsed family members. Frequency values are left to the enum documentation.

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 ('Find ABS statistical tables (dataflows)') plus the searchable dimensions: topic words, geography level, frequency. It also names its downstream sibling ('then describe_table'), so an agent can place it in the workflow without opening the 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?

Explicit entry-point guidance ('Start here, then describe_table') and a concrete querying strategy for situation-style requests ('search for each thing it depends on'). It also tells the agent to use the geography filter when a family is collapsed. The gap is that sibling tools named 'search' and 'search_options' are never contrasted, leaving some routing ambiguity.

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

All ABS Data (observed) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.