Skip to main content
Glama

script_validate

Read-onlyIdempotent

Validate a cubicle.script v1 (the YAML text) with the reference validator: the JSON report with every diagnostic (codes C000–C095, file:line:col) and the budget (warm-up bars, memory, nodes per bar), and explained: every diagnostic beside its code's title and what the code means, in the runner's own words. Nothing runs. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "script": "<script>"
    },
    "name": "script_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
scriptYesthe cubicle.script v1 YAML text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: it makes non-execution explicit, signals zero cost, and enumerates what the report contains (diagnostics with codes and file:line:col, a budget section, and an 'explained' section).

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?

Everything is packed into one front-loaded sentence led by the core verb and resource, followed by terse fragments. The parenthetical code range and budget list are dense but each clause carries information; 'Free.' is a deliberate, useful fragment.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so by describing the JSON report, diagnostic code range, and the 'explained' mapping. For a one-parameter, non-executing tool this is close to complete, missing only anything about failure modes such as unparseable YAML.

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?

There is a single required parameter at 100% schema coverage, and the schema already says it is the cubicle.script v1 YAML text. The description restates the same fact without adding format, size, or validation-precondition detail, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Validate a cubicle.script v1 ... with the reference validator') and pins the input form (the YAML text). It implicitly separates itself from execution-oriented siblings with 'Nothing runs', though it never names an alternative tool explicitly.

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

Usage Guidelines3/5

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

'Nothing runs. Free.' implies the usage context (static checking before spending anything on a run) but never states when to prefer this over a sibling such as rehearse or explain. The guidance is inferable rather than explicit, with no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources