sg-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SG_ELI_BASE_URL | No | Base URL for Singapore Statutes Online | https://sso.agc.gov.sg |
| SG_ELI_AUDIT_DIR | No | Directory for audit logs | ~/.matematic/audit |
| SG_ELI_CACHE_DIR | No | Directory for caching responses | ~/.matematic/cache/sg-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 |
|---|---|
| sg_list_actsA | Browse Singapore's current Acts (paginated - SSO has no keyword search API). |
| sg_get_provisionA | Fetch the text of one numbered section of an act. |
| sg_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:
|
| sg_get_full_textA | Fetch the full text of an act. Large acts are truncated. |
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 targets a distinct action: listing acts, retrieving a single provision, retrieving full act text, and exposing connector coverage. There is no meaningful overlap that would cause an agent to select the wrong tool.
Three tools follow a consistent sg_<verb>_<noun> pattern: sg_list_acts, sg_get_provision, and sg_get_full_text. The outlier is sg_coverage, which uses a bare noun instead of a verb_noun form, but the naming remains predictable overall.
Four tools is a well-scoped size for a focused read-only legal retrieval connector. Each tool covers a distinct core need, and there are no redundant or unnecessary additions.
The set covers listing acts, fetching full text, and fetching individual provisions, with an explicit coverage tool that documents known gaps and fallbacks. It lacks a section index and paginated full-text continuation for large acts, but those gaps are surfaced rather than hidden.