eRegulations MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EREGULATIONS_API_URL | Yes | URL of the eRegulations API to connect to |
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listProceduresA | List all available procedures in the eRegulations system. |
| getProcedureDetailsA | Get detailed information about a specific procedure by ID. |
| getProcedureStepB | Get information about a specific step within a procedure. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| listProcedures | Get a list of all available procedures in the eRegulations system |
| getProcedureDetails | Get detailed information about a specific procedure by its ID |
| getProcedureStep | Get information about a specific step within a procedure |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: listing all procedures, retrieving a specific procedure's details, and getting a specific step within a procedure. There is no overlap or confusion between these operations.
All tool names follow a consistent camelCase verb_noun pattern: listProcedures, getProcedureDetails, getProcedureStep. The naming is uniform and predictable.
Three tools is slightly on the lower end but reasonable for a focused read-only procedures lookup server. Each tool serves a clear purpose, and the count is not thin enough to feel incomplete.
The server covers the essential read operations for procedures and steps. A minor gap is the lack of a search or list steps function, but the core lookup workflow is supported.