Skip to main content
Glama

validate_change

Read-only

Validate an OpenSpec change with the pinned official CLI and return findings even when validation fails, so you can review issues before applying changes.

Instructions

Validate an OpenSpec change with the pinned official CLI; returns findings even when validation fails.

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": {
      "id": "<id>"
    },
    "name": "validate_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
workspacePathNoTrusted absolute project path from this chat; pass on every call. null selects personal storage. Omission uses only the environment default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with them. It adds genuine context beyond the annotations: validation runs via a 'pinned' CLI (deterministic version) and findings are returned even when validation fails, so the agent knows a failed validation is a successful call, not an error. It stops short of describing finding severity or format.

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?

A single front-loaded sentence with no filler; the semicolon cleanly separates purpose from the return-behavior caveat. Nothing is wasted, though the extreme brevity leaves gaps that belong in other dimensions.

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?

For a two-parameter read-only tool with no output schema, the description covers purpose and the key return behavior (findings on failure). It is incomplete on the required 'id' argument and on what the findings contain, which an agent needs to interpret the result.

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

Parameters2/5

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

Schema coverage is only 50%: workspacePath is well documented in the schema, but the required 'id' parameter has no schema description and the description does not clarify what it is (change ID, slug, or name) or how to obtain it. The description adds no parameter meaning beyond the bare phrase 'an OpenSpec change'.

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 gives a specific verb and resource: 'Validate an OpenSpec change', plus the mechanism ('pinned official CLI'). That is clearly distinct from siblings like change_status or read_change, though the description itself never names an alternative to reinforce the distinction.

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?

Usage is implied rather than stated: an agent can infer this is the tool for checking a change's conformance. There is no explicit guidance on when to run it (e.g. before archive_change), no prerequisites, and no exclusions pointing to sibling tools.

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