Semantic Layer Gap Closure MCP Server
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| semantic_checkA | Interpret a domain message against the governed glossary and field contracts before an agent acts. Returns proceed, escalate or block with a trace. Anything uncertain escalates. |
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 1 tool
There is only one tool, so there is no intra-server ambiguity or risk of misselecting between overlapping tools. Its purpose as a pre-action semantic gate is clearly distinguishable from ordinary data operations.
The single tool uses a readable snake_case name with a clear semantic meaning. Consistency cannot truly be assessed across one tool, but the naming style is predictable and not confusing.
A single tool is thin for a server framed as closing semantic-layer gaps. It can serve as a focused gate, but the scope implied by the server name suggests more lifecycle support would be expected.
The surface only supports checking a message and returning proceed/escalate/block. There are no tools for managing glossary terms, field contracts, gap records, traces, or escalation resolution, which are significant gaps for a semantic-layer gap-closure server.