Skip to main content
Glama

latest

Retrieve the most recent reporting year data for any WGEA dataset. Filter by employer or industry to get current workforce composition, pay gaps, or parental leave metrics.

Instructions

Return rows from the most recent WGEA reporting year for a dataset.

Trims to the single latest reporting_year — useful for "what's the current gender breakdown at CBA?" without having to remember WGEA's annual cadence.

Examples: # Latest workforce composition at CBA resp = await latest("WORKFORCE_COMPOSITION", filters={"employer_name": "Commonwealth Bank"})

# Cap rows (portfolio-standard name)
resp = await latest("WORKFORCE_COMPOSITION",
                    filters={"anzsic_division": "Mining"}, limit=100)

# Legacy alias still works
resp = await latest("WORKFORCE_COMPOSITION",
                    filters={"anzsic_division": "Mining"}, max_rows=100)

Parameter notes: - Prefer limit (portfolio-standard; matches asic-mcp's latest(..., limit) parameter). - max_rows retained as legacy alias. - Supplying both raises ValueError — pick one. - get_data() keeps max_rows unchanged (separate surface, separate concern).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYesCurated dataset ID.
filtersNoSame filter shape as get_data. Useful for narrowing to one employer.
limitNoCap on returned rows (portfolio-standard name). Default 2000, max 10000. Mutually exclusive with the legacy `max_rows` alias — supplying both raises ValueError.
max_rowsNoLegacy alias for `limit` — retained for backward compatibility (wgea-mcp <= 0.4.x). Prefer `limit` for cross-sister consistency with asic-mcp's `latest(..., limit)` parameter. Same semantics as `limit`. Supplying both raises ValueError.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYes
dataset_nameYes
queryNo
reporting_yearNo
periodNoCanonical period bounds {start, end} for cross-sister consumers. Populated alongside the wgea-specific reporting_year. For a single reporting year both bounds match; for multi-year spans they bracket the range.
unitNo
row_countNo
recordsNo
csvNo
sourceNoWorkplace Gender Equality Agency
attributionNoSource: Workplace Gender Equality Agency. Licensed under Creative Commons Attribution 3.0 Australia (https://creativecommons.org/licenses/by/3.0/au/). Original dataset: https://data.gov.au/data/dataset/wgea-dataset
retrieved_atYes
source_urlYes
download_urlNo
did_you_meanNo
staleNo
stale_reasonNo
truncated_atNo
server_versionNo
Behavior4/5

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

No annotations provided, so description carries burden. Describes behavior as returning rows and trimming to latest year. Implies read-only operation, but does not explicitly state non-destructive nature. Adequate for a query tool.

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?

Well-structured: purpose statement, examples, parameter notes. Each sentence adds value without redundancy. Appropriate length for the tool's complexity.

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?

Covers main use case, parameter interactions, and examples. References sibling get_data for context. Output schema exists, so return format not needed. Complete for a filtered data retrieval tool.

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 100%, baseline 3. Description adds value by explaining parameter relationship (limit vs max_rows mutual exclusivity), providing usage examples, and giving rationale for preferring limit. Adds beyond schema.

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?

Description clearly states it returns rows from the most recent WGEA reporting year, with examples showing current snapshot use. Distinguishes from siblings like get_data by trimming to latest year.

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?

Provides explicit use case (current gender breakdown) and examples. Parameter notes clarify limit vs max_rows. Does not explicitly state when not to use or mention alternatives among siblings, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bigred97/wgea-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server