Skip to main content
Glama

run_checks

Run checks from netdryrun.yml against an already-running lab and get a pass, fail, or inconclusive verdict—without deploying or destroying it.

Instructions

Run the checks in netdryrun.yml at path against a lab that is already running (no deploy, no destroy), such as one kept with dry_run keep_lab=true. Same result and verdict as dry_run. Configs edited after the lab started do not reach it: to test a change, use dry_run. 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": "run_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.9/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 behavioral burden and does so thoroughly: it discloses the no-deploy/no-destroy scope, duration, Linux/WSL2/Docker/containerlab requirements, macOS/sandbox limitations, and the meaning of INCONCLUSIVE or setup errors. It also forbids weakening checks, which is important safety behavior.

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?

The first sentence front-loads the core action and scope, and subsequent sentences each add necessary constraints: when to use it, platform requirements, duration, failure semantics, and alternatives. Despite its length, no sentence is redundant or unrelated to correct invocation.

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?

The tool is complex and has no annotations, but the description covers prerequisites, runtime expectations, failure states, and sibling alternatives. An output schema exists, so the description is not required to explain return values. Nothing critical for safe invocation appears to be missing.

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?

Schema coverage is 0%, so the description must explain the lone `path` parameter. It clarifies that `path` locates netdryrun.yml, adding meaningful context beyond the schema's bare `Path` title. It does not specify whether the path is absolute, relative, file-only, or directory, so it is strong but not complete.

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?

The description states a specific verb and resource: run the checks in netdryrun.yml at `path` against an already running lab. It explicitly distinguishes this from dry_run by noting no deploy/destroy and that config edits after lab start do not reach it. An agent can identify the tool's role without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance ('before proposing or applying any routing or policy change') and alternatives: use dry_run to test a change, record_baseline or verify_change when no checks exist. It also says INCONCLUSIVE means stop and not to retry more than once, covering failure handling.

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