octave-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 | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| octave_validateA | Schema check + repair suggestions for OCTAVE content. Validates content against schema, returns canonical form with optional repairs. Focus on I3 (Mirror Constraint) and I5 (Schema Sovereignty). |
| octave_writeA | Unified entry point for writing OCTAVE files. Handles creation (new files) and modification (existing files). Use content for full payload, changes for delta updates. Omit both content and changes to normalize an existing file in-place. Replaces octave_create and octave_amend. |
| octave_ejectA | Eject OCTAVE content with projection modes. Supports canonical, authoring, executive, and developer views. Can generate templates when content is null. Output formats: octave, json, yaml, markdown, gbnf. |
| octave_compile_grammarA | Compile OCTAVE schema or contract to constraint grammar. Supports GBNF (llama.cpp) and JSON Schema (vLLM) output formats. Provide either a builtin schema name or inline OCTAVE content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| grammar/AGENT_DEFINITION | Pre-compiled GBNF grammar for the AGENT_DEFINITION schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/COGNITION_DEFINITION | Pre-compiled GBNF grammar for the COGNITION_DEFINITION schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/CRS_REVIEW | Pre-compiled GBNF grammar for the CRS_REVIEW schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/DEBATE_TRANSCRIPT | Pre-compiled GBNF grammar for the DEBATE_TRANSCRIPT schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/DECISION_LOG | Pre-compiled GBNF grammar for the DECISION_LOG schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/META_SCHEMA | Pre-compiled GBNF grammar for the META_SCHEMA schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/SKILL | Pre-compiled GBNF grammar for the SKILL schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
| grammar/TEST_HOLOGRAPHIC | Pre-compiled GBNF grammar for the TEST_HOLOGRAPHIC schema. Use with llama.cpp --grammar flag or similar constrained decoding engines. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: compiling grammars, ejecting content in various formats, validating and repairing content, and writing files. There is no overlap or ambiguity.
All tools use the 'octave_' prefix and snake_case, but the verb pattern is not fully uniform: 'compile_grammar' is verb_noun while 'eject', 'validate', and 'write' are single verbs. This minor deviation reduces consistency slightly.
Four tools is well-scoped for a specialized server dealing with OCTAVE content management. Each tool serves a necessary function without redundancy or unnecessary excess.
The tools cover core operations (compile, eject, validate, write), but there is no explicit read/list or delete tool, which may be a minor gap depending on the expected workflow. The focus on writing and validation is evident, but a complete lifecycle is not fully covered.