GovWait
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_entitiesB | Search tracked government processing-time routes by free text (service and/or country, e.g. 'canada study permit pakistan'). Returns matching entity_ids with latest source-backed values and collection status. |
| get_entityA | Get one route by entity_id (e.g. 'ca-visitor-visa--in'): latest retained value, collection status, and full recorded history. Forward-looking IRCC routes also include application-month cohort estimates. |
| get_latest_valueA | Get the latest retained official processing-time record for a service, optionally for a specific applicant country. Check source_collection_status before treating it as current. New Zealand services return both 50% and 80% records. |
| compare_valuesB | Compare latest source-backed processing-time records for one service across several applicant countries, sorted fastest first and labeled with collection status. |
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 4 tools
search_entities and compare_values have clearly distinct roles (free-text discovery vs. cross-country comparison). However, get_entity and get_latest_value overlap: both return the latest retained processing-time record, differing mainly in that get_entity adds full history and cohort estimates. The descriptions do clarify this, but an agent could still misselect between them.
All four tools follow a clean snake_case verb_noun convention: get_entity, get_latest_value, compare_values, search_entities. The verbs (get, compare, search) are predictable and consistently used.
Four tools is a lean but sensible scope for a focused read-only processing-time lookup service. It is on the thin side—no bulk/list-all operation—but each tool earns its place.
The surface covers the core read-only lifecycle: discovery (search_entities), single-record retrieval (get_entity, get_latest_value), and comparison (compare_values). As a data-browsing service no create/update is expected; only minor gaps like bulk retrieval or listing all sources remain.