my-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MY_ELI_BASE_URL | No | Base URL for lom.agc.gov.my | https://lom.agc.gov.my |
| MY_ELI_AUDIT_DIR | No | Audit log directory | ~/.matematic/audit |
| MY_ELI_CACHE_DIR | No | Cache directory for fetched data | ~/.matematic/cache/my-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 |
|---|---|
| my_get_actA | Fetch metadata for a Malaysian principal Act by its numeric act coordinate. |
| my_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:
|
| my_get_textB | Fetch the full text of a Malaysian principal Act (extracted from its official PDF). |
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
The three tools are largely distinct: one fetches metadata, one fetches full text, and one declares coverage/gaps. The only potential confusion is between my_get_act and my_get_text, but their descriptions clearly separate metadata from full text.
Two tools follow a get_<object> pattern (my_get_act, my_get_text), but my_coverage uses a noun instead of a verb, breaking the pattern. The my_ prefix is consistent, but the mixed verb/noun structure is a minor inconsistency.
Three tools is on the lower end but reasonable for a narrowly scoped connector that serves act metadata, act text, and coverage declarations. It feels slightly thin but not inadequate for its stated purpose.
The connector covers fetching individual acts and declaring coverage gaps, but lacks obvious operations like listing all acts or searching across acts. The coverage tool helps mitigate the absence, but the surface remains somewhat incomplete for a legal research tool.