FREE. Catalog of all ausref reference-data series: supported countries, series ids, descriptions, freshness metadata and per-series URLs. Call this first to discover what data exists.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states that the tool is 'FREE' and describes the return content, but does not discuss any potential side effects, rate limits, or data freshness guarantees. For a read-only catalog tool, this is adequate but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is concise and front-loaded with 'FREE.' It includes all essential information without extraneous words, earning its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters, no output schema, and no annotations, the description is fairly complete. It tells the agent to call this first for discovery and lists what is returned. However, it lacks details about pagination, response size limits, or format, but overall it is adequate for the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so schema coverage is 100%. The description adds value by explaining that the tool returns a catalog of series, which is useful context. With no parameters, a baseline of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it lists a catalog of all ausref reference-data series, including specific content like countries, series ids, descriptions, freshness metadata, and URLs. It uses the specific verb 'catalog' and resource 'series', and distinguishes from siblings by advising to call this first.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Call this first to discover what data exists,' providing clear usage guidance. It implies this is a discovery tool before using other tools like get_series, but does not explicitly mention when not to use it or alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct domain: wage compliance, income tax, VAT, working days, holidays, series data (current, history, snapshot, catalog), and settlement dates. Even the financial computations (check_minimum_wage, compute_income_tax, compute_vat) have clearly different inputs and purposes, so no two tools are confusable.
Most tools follow a clear verb_noun snake_case pattern (check_, compute_, count_, get_, list_). The only exception is `settlement_date`, which is a noun phrase rather than verb-first, but it remains consistent in style and readability. This minor deviation prevents a perfect score.
With 10 tools, the server is well-scoped for a reference-data provider. It balances specific computations (minimum wage, tax, VAT) with general data access (series, holidays, settlements), and each tool serves a clear purpose without overlap or unnecessary bulk.
The tool surface comprehensively covers reference data for financial and calendar domains: statutory rates and compliance, holiday and working-day calendars, settlement conventions, and a generic series system with current, historical, snapshot, and catalog access. No obvious gaps impede an agent from accomplishing typical reference-data tasks, and the free list_series enables discovery.
