co-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CO_ELI_BASE_URL | No | Base URL for the datos.gov.co API. | https://www.datos.gov.co/resource/v2k4-2t8s.json |
| CO_ELI_AUDIT_DIR | No | Audit directory for the co-eli MCP server. | ~/.matematic/audit |
| CO_ELI_CACHE_DIR | No | Cache directory for the co-eli MCP server. | ~/.matematic/cache/co-eli |
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 |
|---|---|
| co_search_sentenciasA | Free-text search over Corte Constitucional decision metadata. |
| co_coverageA | Declare what this connector covers, how it is sourced, and what it does NOT cover. Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead. Returns:
|
| co_get_sentenciaA | Verify a Corte Constitucional citation and fetch its metadata. |
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 3 tools
Each tool has a clearly distinct purpose: search for finding decisions, get for fetching metadata by citation, and coverage for understanding connector limitations. There is no overlap or ambiguity between them.
Two tools follow a clear co_verb_noun pattern (co_search_sentencias, co_get_sentencia), while co_coverage is a noun-only name. This is a minor deviation but the pattern remains readable and predictable.
With only 3 tools, the server is tightly scoped to the task of searching and retrieving Colombian constitutional decisions. Each tool earns its place, and the count feels appropriate for the connector's focused purpose.
The core workflows of searching, retrieving, and verifying decisions are covered. The coverage tool explicitly documents gaps and fallbacks, which mitigates potential missing functionality. A minor gap is the lack of a listing or browsing tool, but search handles that sufficiently.