Skip to main content
Glama

validate_scope

Read-onlyIdempotent

Recommends relevant validation checks and commands after code edits, using known changed files when provided and inferring scope from the task otherwise.

Instructions

After edit_scope, recommend the most relevant validation checks and commands. Pass files when you already know what changed; they take precedence over task inference.

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": {
      "task": "<task>"
    },
    "name": "validate_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute project root. Omit only where this session started; required elsewhere and on every subagent call.
taskYesTask description or intended change.
filesNoFiles already changed or known to be in scope. These take precedence over task inference.
formatNoReturn plain text or structured JSON. Default: text.
max_filesNoMaximum files to inspect when building validation guidance. Default: 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / root / description
      Previous value: -"Absolute project root. Required with linked worktrees; subagents must pass their own worktree root on every call."New value: +"Absolute project root. Omit only where this session started; required elsewhere and on every subagent call."
  2. First observedv1.4.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description usefully adds that the tool recommends rather than executes checks, and that explicit files override inference, but says nothing about scope of inspection, cost, or how many checks are returned.

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 short sentences, zero filler, with the sequencing trigger front-loaded ahead of the parameter hint. Nothing could be removed without losing information.

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

Completeness5/5

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

Covers what the tool returns (validation checks and commands) and the one non-obvious calling rule, and the remaining parameters are fully documented in schema. With no output schema, a brief return-value statement would help, but this is a minor gap rather than a missing one.

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 every parameter including root, format and max_files is already documented, establishing a baseline of 3. The description's files-precedence note merely restates the schema text for that property and adds no syntax or format detail beyond it.

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 and output ("recommend the most relevant validation checks and commands") plus a sequencing cue ("After edit_scope"). The agent knows this produces validation guidance rather than performing edits, but no sibling in the provided list is named as an alternative, so differentiation relies on inference.

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

Usage Guidelines4/5

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

Gives a clear invocation point ("After edit_scope") and a decision rule for the optional files parameter ("Pass files when you already know what changed; they take precedence over task inference"). No when-not-to-use guidance or explicit alternative tool is offered.

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