mcp-impo
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 |
|---|---|
| schemaA | Retrieve IMPO JSON schema documentation. Returns the JSON schema defining the structure for normas and avisos from IMPO's datos abiertos API. This schema describes all available fields for Uruguayan legislation and official notices. |
| normaC | Get a specific norma or aviso from IMPO. Retrieves detailed information about a specific legal norm or notice from IMPO's database in JSON format. |
| searchB | Search for normas or avisos in IMPO database. Performs a search across IMPO's database of Uruguayan legislation and official notices. Results can be filtered by type and year. |
| basesA | Get information about available bases in IMPO. Returns metadata about the available databases and their structure from IMPO's datos abiertos service. |
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: 'bases' retrieves database metadata, 'schema' provides the data structure, 'search' performs queries, and 'norma' fetches a specific record. No overlap or ambiguity.
Tool names are all single lowercase nouns (bases, norma, schema, search), following a consistent, predictable pattern without mixing conventions.
Four tools is well-scoped for a legislation/norm search service: metadata, schema, search, and retrieval cover the core functionality without excess or deficiency.
The set covers key operations: explore databases, understand schema, search, and retrieve specific items. Missing a direct 'list all normas' endpoint, but search can approximate it, so minor gap.