Data.gov MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| package_searchC | Search for packages (datasets) on Data.gov |
| package_showB | Get details for a specific package (dataset) |
| group_listB | List groups on Data.gov |
| tag_listC | List tags on Data.gov |
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
Each tool has a clearly distinct purpose targeting different resources: groups, packages (datasets), and tags. The actions (list, search, show) are well-defined and non-overlapping, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure (e.g., group_list, package_search). This predictability enhances readability and usability across the tool set.
With only 4 tools, the set feels thin for a data portal server, lacking operations like create, update, or delete for resources. While the tools cover basic read/search functions, the scope could be expanded for more comprehensive coverage.
The tool surface is severely incomplete for a data management domain, missing essential CRUD operations (e.g., no create_package, update_package, delete_package) and other common actions like resource_show for groups or tags. This will likely cause agent failures when trying to perform full lifecycle tasks.