Skip to main content
Glama

octave_validate

Validates OCTAVE content against schema definitions, providing canonical form and optional repair suggestions for Mirror Constraint and Schema Sovereignty issues.

Instructions

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentNoOCTAVE content to validate (mutually exclusive with file_path)
file_pathNoPath to OCTAVE file to validate (mutually exclusive with content)
schemaYesSchema name to validate against (e.g., 'META', 'SESSION_LOG')
fixNoIf True, apply repairs to canonical output. If False (default), suggest repairs only.
debug_grammarNoIf True, include compiled regex/grammar in output for debugging constraint evaluation.
grammar_hintNoIf True and validation returns INVALID, include compiled GBNF grammar in response to guide correction.
diff_onlyNoIf True, return diff instead of canonical content. Saves tokens when validating.
compactNoIf True, return warning/error counts instead of full lists. Saves tokens.
profileNoValidation strictness profile: STRICT (full compliance, reject unknown), STANDARD (default), LENIENT (warnings not errors, auto-repairs), ULTRA (minimal validation).
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must fully disclose behavior. It mentions validation and repair but does not clarify whether repairs write back to files or affect state. The 'fix' parameter's effect is ambiguous, and there is no discussion of permissions, side effects, or output format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with core purpose, no unnecessary words. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Handles overall function but lacks detail on parameter interactions (e.g., mutual exclusivity of content/file_path) and behavioral specifics like output when fix is applied. With no output schema, more context on return values would help.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. Description adds minimal extra context (e.g., focusing on I3 and I5 schemas), but does not significantly enhance understanding beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool validates OCTAVE content against a schema and can repair it. It mentions focus on I3 and I5, which distinguishes it from sibling tools like octave_compile_grammar or octave_write. However, the terms I3 and I5 are not explained, slightly reducing clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus its siblings or when not to. The description implies use for validation/repair but does not state alternatives or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elevanaltd/octave-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server