utsunomiya-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
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 |
|---|---|
| list_datasetsA | List available datasets from Utsunomiya city. Returns a list of available datasets with their IDs, names, and descriptions. Use this to discover what data is available before querying. |
| search_datasetsB | Search for datasets in the Utsunomiya Open Data Catalog. |
| get_dataset_schemaB | Get schema information for a specific dataset. |
| query_datasetB | Query dataset contents with optional filtering. |
| analyze_datasetC | Perform statistical analysis on a dataset. |
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 5 tools
Each tool has a clearly distinct purpose: listing, searching, schema retrieval, querying, and analysis. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using underscore_case (e.g., list_datasets, query_dataset).
5 tools is appropriate for an open data portal, covering essential operations without being too few or too many.
The tool set covers the full lifecycle of dataset interaction: discovery (list/search), metadata (schema), data retrieval (query), and analysis (analyze). No obvious gaps.