Skip to main content
Glama

octave_validate

Validates OCTAVE content against a schema, providing canonical output and repair suggestions. Supports configurable strictness profiles and optional auto-repairs.

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).
Behavior3/5

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

With no annotations, the description provides some behavioral details like optional repairs, diff output, and debugging info, but does not disclose side effects, permissions, or error behavior.

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

Conciseness4/5

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

The description is concise with two sentences, front-loading the main purpose. It could be more structured but is not verbose.

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

Completeness2/5

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

The description fails to explain return format or behavior in detail (e.g., what 'canonical form' looks like, error handling), despite having no output schema and 9 parameters.

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 coverage is 100%, so baseline is 3. The description adds token-saving notes for diff_only and compact, and explains profiles, but does not add significant meaning beyond the schema.

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

Purpose5/5

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

The description clearly states 'Schema check + repair suggestions for OCTAVE content' and specifies focus on I3 and I5 constraints, distinguishing it from sibling tools like octave_compile_grammar and octave_write.

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 alternatives like octave_write or when to avoid it. No exclusions or prerequisites are mentioned.

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