GovNavigator
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ordinanceA | Search Madison, WI municipal code/ordinances for specific topics. Use this tool when users ask about:
Returns relevant ordinance sections with citations. Examples of good queries:
|
| get_ordinance_detailsA | Get full details of a specific ordinance section by title. Use this after search_ordinance to get more details about a specific section. |
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 2 tools
The two tools have clearly distinct purposes: search_ordinance finds relevant ordinance sections based on topics, while get_ordinance_details retrieves full details for a specific section. There is no overlap or ambiguity between them, as one is for discovery and the other for detailed lookup.
Both tools follow a consistent verb_noun pattern (search_ordinance and get_ordinance_details) with clear, descriptive names. The naming convention is uniform and predictable across the tool set.
With only two tools, the server feels thin for its apparent scope of navigating municipal codes and ordinances. While the tools cover search and detail retrieval, the lack of additional operations like listing ordinances, updating information, or handling related processes suggests an incomplete surface for the domain.
The tool set is severely incomplete for a municipal code navigation server. It only supports search and detail retrieval, missing essential operations such as listing ordinances, accessing related documents, or providing updates. This creates significant gaps that could hinder agent workflows in this domain.