prism-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRISM_DISABLE_MEASURE | No | Set to 1 to disable all inference (measurement) while leaving preflight fully available. |
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 |
|---|---|
| prism.preflightA | Select 3-5 useful perspectives for a task and return the claim-packet contract the host should follow. Deterministic and offline. Reads packaged registry data only: no user-project files, no network, no credentials. |
| prism.measureA | Measure contradictions, scope divergence, duplicates, and internal conflicts across 2-5 candidate claim packets using local CPU encoders. Bounded runtime. Reads only the verified local model bundle and the supplied input; mutates nothing and reaches no network. Reports conflict, never truth. |
| prism.synthesis_contractA | Return the rules the host must follow when writing the final answer: which conflicts to disclose, which distinct claims to preserve, and which shortcuts are prohibited. Deterministic; generates no prose. |
| prism.healthA | Report local health. Shallow mode checks contracts and the perspective registry. Deep mode additionally verifies model artifact hashes, asserts the CPU execution provider, and runs one synthetic inference. Never scans the user's project or environment. |
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 4 tools
Each tool has a clearly distinct purpose: preflight selects perspectives, measure evaluates conflicts, synthesis_contract defines output rules, and health checks the system. There is no overlap or ambiguity between them.
All names use consistent lowercase snake_case, but the syntactic pattern is mixed: preflight and measure are verbs, while synthesis_contract and health are nouns. This is a minor deviation from a strict verb_noun convention, but the names remain readable and predictable.
With only 4 tools, the server is tightly scoped around its purpose of claim-packet analysis and synthesis. Each tool is essential to the workflow, and the count is neither too sparse nor excessive.
The server covers the full lifecycle of the analysis process: selecting perspectives (preflight), measuring contradictions (measure), obtaining synthesis rules (synthesis_contract), and verifying system health (health). No critical operations are missing for the stated deterministic, offline analysis domain.