Skip to main content
Glama

check_types

Lists supported check types and their keys to help read or write netdryrun.yml; starts no lab.

Instructions

List supported check types and their keys, to read netdryrun.yml or help a human write it. Starts no lab. 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

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": "check_types"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key trait: 'Starts no lab' means a side-effect-free read. However, most of the remaining behavioral text (60–120 s runtime, Linux/WSL2/Docker/containerlab requirements, INCONCLUSIVE/error semantics, retry limits) describes the dry-run workflow rather than this listing tool, so the genuinely tool-specific disclosure is thin.

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 first two sentences are front-loaded and on point, but roughly nine further sentences cover the Netdryrun workflow at large — timing, platform requirements, INCONCLUSIVE handling, anti-gaming advice — none of which help an agent decide to call or correctly invoke a zero-argument type-listing tool. This reads as server-wide boilerplate pasted into a narrow tool.

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?

An output schema exists, so return values need not be explained, and the tool-specific guidance present is accurate. But for a listing tool the description never says what a 'check type' or 'key' is in practice or how the listing relates to netdryrun.yml fields, while spending most of its length on unrelated dry-run policy.

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 the baseline is 4. The phrase 'and their keys' hints at the shape of each entry, and an output schema exists to document the return structure, so nothing further is required.

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 opening sentence states a specific verb and resource — 'List supported check types and their keys' — and adds 'Starts no lab', which implicitly separates it from the dry_run/start_run siblings. It is clear what the tool returns, though it never names a sibling tool explicitly.

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?

It gives two concrete use cases (reading netdryrun.yml, helping a human write it) and later routes the agent elsewhere when no checks exist: 'call record_baseline, or verify_change'. There is no explicit statement of when to call this versus dry_run for inspection, but the 'Starts no lab' clause covers the main confusion.

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