OpenGATE
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_groundingA | Check whether an answer is grounded in the provided context. Deterministic (no LLM judge): verifies that required facts appear in the answer, that every number in the answer traces to the context, and — for questions the context cannot answer — that the answer abstains instead of fabricating. Use this to self-check RAG / document-QA / retrieval answers before returning them. |
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 possibility of confusing it with another tool. Its purpose—deterministically checking answer grounding—is clearly distinct and described in detail.
The single tool name uses a clean verb_noun structure (check_grounding) and matches the server's purpose. With only one tool, there are no inconsistent conventions to create confusion.
At one tool, the surface is at the absolute minimum and feels thin compared to typical MCP servers. However, the tool is non-trivial and the server appears intentionally focused on a single grounding-check task, making it borderline rather than egregious.
For its stated purpose, the tool covers the major grounding requirements: required facts, numeric traceability, and abstention on unanswerable questions. It lacks related conveniences such as batch checking or detailed failure explanations, but no critical operation for the core workflow is missing.