Skip to main content
Glama

project_validate

Checks the working copy for problems introduced by changes—duplicate IDs, broken references, and permissions—and warns about layout issues in new blocks before saving.

Instructions

Checks the working copy for problems introduced by the changes (duplicate IDs, broken references, permissions) and warns about layout issues of new blocks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does useful work by naming the categories checked and flagging layout warnings, which hints at a diagnostic/read-only purpose, but it never states that the tool is non-mutating, whether it fails or merely reports, whether it inspects saved state versus in-memory edits, or what permissions are required.

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?

A single front-loaded sentence with a parenthetical enumeration that earns its space by specifying the exact defect classes checked. No filler, no restatement of the title.

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?

For a zero-parameter tool with no output schema and no annotations, the description tells the agent what is inspected and what kinds of findings to expect ('problems' and 'warnings'). It falls short only on the result shape (errors vs warnings, pass/fail signal) and on the relation to the sibling lint tool.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly avoids inventing inputs.

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?

States a specific verb ('Checks') and resource ('the working copy') and enumerates the problem classes it looks for: duplicate IDs, broken references, permissions, plus layout warnings for new blocks. An agent grasps what the tool does immediately, but nothing distinguishes it from the sibling project_lint, which by name reads as an overlapping validation tool.

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 only implied by the phrase 'problems introduced by the changes', which suggests running it after edits. It gives no explicit when-to-use trigger, no prerequisites (e.g. must the project be open or saved), and does not mention project_lint or any alternative, leaving the agent to guess which validation tool to call.

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