Skip to main content
Glama

validate

Checks a netdryrun.yml file without launching a lab, confirming node names, drivers, and supported keys before deployment and returning check names or the error—not a routing verdict.

Instructions

Validate netdryrun.yml at path without starting a lab (takes seconds): node names, drivers and supported keys, as dry_run checks them before deploying. Returns the check names or the error. It is not a verdict: run dry_run next. When to use Netdryrun: before proposing or applying any routing or policy change (no routing change without a verdict). Ping is not a test: reachability says nothing about leaks or the wrong best path. A dry run takes about 60–120 s. Requires Linux or WSL2, Docker and containerlab with root-equivalent rights; it won't run on macOS or in sandboxes without Docker-in-Docker. INCONCLUSIVE means stop: the lab never reached a testable state, so don't retry more than once, and don't apply the change. Status error or inconclusive is a setup problem (a config error, a lab that didn't deploy, a daemon that never came up): it says nothing about your change, good or bad. Never invent or weaken checks to make a change pass: if no checks exist, call record_baseline, or verify_change with the intent the ticket states.

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": {
      "path": "<path>"
    },
    "name": "validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: seconds-long runtime, what it returns (check names or the error), platform prerequisites (Linux/WSL2, Docker, containerlab, root-equivalent; no macOS, no sandboxes without DinD), and how to read INCONCLUSIVE versus status error. That is exactly the operational context an agent needs before calling.

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

Conciseness2/5

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

The useful core is front-loaded well, but the text runs long and several sentences do not pertain to this tool: 'Ping is not a test', the blanket 'no routing change without a verdict' policy, and the record_baseline/verify_change fallback instructions belong to sibling tools or to shared documentation.

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?

An output schema exists, so return-value detail is not required, and the description nonetheless signals the shape ('check names or the error'). Setup requirements, failure semantics and the next-step dependency are all covered, leaving little an agent would still need to guess.

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?

One required parameter with 0% schema coverage, so the description must compensate. It does partially by identifying `path` as the location of netdryrun.yml, telling the agent what kind of value to supply, though it does not state whether the path is relative/absolute or what happens if the file is absent.

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?

States a specific verb and resource ('Validate netdryrun.yml at `path` without starting a lab') and enumerates what is checked: node names, drivers, supported keys. It also distinguishes itself from the nearest sibling by framing itself as a fast pre-check that is 'not a verdict' versus dry_run.

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?

Explicitly routes the agent: 'It is not a verdict: run dry_run next', plus policy-level guidance on when routing changes require a verdict. However, the 'When to use Netdryrun' block reads as family-wide policy rather than guidance specific to this validate step, which dilutes precision.

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