DatumGuard 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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| design_contract_draftC | Draft a contract without inferring ambiguous numbers or units. |
| design_contract_validateA | Normalize and validate a DesignContract for deterministic generation. |
| drawing_generateC | Generate an unverified R2013 DXF and SVG preview. |
| drawing_verifyC | Independently re-read and remeasure serialized DXF bytes. |
| repair_proposeC | Propose bounded changes to declared free parameters only. |
| repair_applyC | Apply an accepted repair after enforcing locked/free policy. |
| drawing_compareC | Compare two contract revisions by public dimension and feature IDs. |
| export_bundleB | Regenerate, independently verify, and write an approved bundle locally. |
| rhino_previewC | Report Rhino preview availability as secondary evidence only. |
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 9 tools
Each tool has a distinct purpose: contract drafting/validation, drawing comparison/generation/verification, exporting, repair proposal/application, and preview. No overlap.
All tools follow a consistent verb_noun pattern with underscores (e.g., design_contract_draft, drawing_compare). No mixing of conventions.
With 9 tools, the set is well-scoped for the domain, covering contract design, drawing operations, repair, and export without being excessive.
The tool set covers the full lifecycle: draft, validate, generate, verify, export, and repair. No obvious gaps for the stated purpose.