wgea-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_datasetsA | Fuzzy-search the curated WGEA dataset catalog. All seven curated datasets cover the WGEA Public Data File: per-employer workforce composition, manager movements, gender-equality policy answers, parental-leave + flexible-work policies, harm-prevention policies, employee support, and workplace overview. Examples: # Find datasets about parental leave results = await search_datasets("parental leave") # → [{id: 'PARENTAL_LEAVE_FLEX', ...}] Returns: List of DatasetSummary (id, name, description, update_frequency, is_curated), ranked by relevance. |
| describe_datasetA | Describe a dataset's filterable dimensions, returnable measures, units, and source. Use this before calling get_data on a new dataset — it tells you the valid filter keys ('employer_name', 'anzsic_division', 'gender', ...), enumerated filter values where they exist (e.g. 'women' → 'Women'), measure aliases ('n_employees'), and the canonical source URL. Returns: DatasetDetail with id, name, description, period_coverage, list of dimensions, list of measures, source_url, and the resolved reporting year label. |
| get_dataA | Query a curated WGEA dataset and return observations. Examples: # Gender breakdown at Commonwealth Bank resp = await get_data( "WORKFORCE_COMPOSITION", filters={"employer_name": "Commonwealth Bank"}, ) Returns: DataResponse with records (or csv), unit, reporting_year, row_count, source URL, the actual download_url used, "did you mean?" fuzzy hints if the employer-name filter didn't match exactly, and CC-BY 3.0 AU attribution. |
| latestA | 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"}) Parameter notes:
- Prefer |
| top_nA | Return the N rows with the largest (or smallest) value of a measure. Ranks across one WGEA reporting year (the latest by default, or a
specific year via Examples: # 10 employers with the most women managers (latest reporting year) top_n("WORKFORCE_COMPOSITION", "n_employees", n=10, filters={"gender": "Women", "manager_category": "Manager"}) Returns:
DataResponse with at most |
| list_curatedA | List every curated dataset ID in this version of wgea-mcp. Returns: Sorted list of dataset IDs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: describe_dataset for metadata, get_data for raw queries, latest for latest year convenience, list_curated for dataset inventory, search_datasets for discovery, and top_n for ranked results. No functional overlap.
Most tools follow verb_noun snake_case (describe_dataset, get_data, list_curated, search_datasets). 'latest' and 'top_n' deviate slightly but are predictable and in line with common conventions for convenience tools.
Six tools is well-scoped for a specialized dataset query server. Each tool addresses a distinct workflow step: discovery, metadata inspection, data retrieval, latest-year convenience, and top-N ranking.
The tool set covers the full exploration-to-query lifecycle: list available datasets, search, describe, query with filters, get latest year, and get top/bottom rows. No obvious gaps for a read-only public data API.