vic-au-important-dates-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASE_URL | No | Base URL for the API (subject to change) | https://wovg-community.gateway.prod.api.vic.gov.au/vicgov/v2.0/ |
| DEVELOPER_VIC_GOV_AU_KEY | Yes | Your developer key from developer.vic.gov.au | |
| DEVELOPER_VIC_GOV_AU_SECRET | Yes | Your developer secret from developer.vic.gov.au |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_datesA | Get a list of important dates for the state of Victoria, Australia. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is clearly defined.
With a single tool, there is no pattern to assess inconsistency. The name 'get_dates' follows a clear verb_noun structure.
The server has only one tool, which is at the low end of typical scoping. While the tool covers many date types via parameters, a slightly larger set (e.g., separate tools for each type) might be more intuitive, but it remains functional.
The tool fully covers the stated domain of important dates for Victoria, Australia, supporting all listed date types (public holidays, daylight saving, school terms, etc.) with flexible date filtering. No obvious gaps exist for a read-only query service.