dmcheck-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| runA | Referee a tabletop session transcript against a table charter. Returns conduct findings (unanswered players, unconsumed rolls, missing cues, spoiler leaks, dead air...), each citing the charter rule violated. False accusations are treated as the worst bug: ambiguity produces silence, not findings. |
| rulesC | The rule set with one-line definitions. |
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 2 tools
The two tools are completely distinct: 'run' executes the analysis and returns findings, while 'rules' simply provides the rule set. There is no overlap or ambiguity between them.
Both names are short, lowercase, and readable, but 'run' is a verb while 'rules' is a noun, so they don't follow a uniform verb_noun pattern. Despite that, the naming is simple and not chaotic.
With only 2 tools, the server is slightly under the typical 3-15 range, but the domain is narrowly scoped to checking transcripts against a rule set. The count feels appropriate for the purpose, with no unnecessary extras.
The tool set fully covers the domain: 'rules' provides the rule definitions, and 'run' applies them to a transcript. There are no obvious missing operations for a read-only checking service.