Skip to main content
Glama

get_result

Retrieve the pass, fail, or inconclusive verdict for a Netdryrun dry run using its run_id; poll after the suggested interval until validation finishes.

Instructions

The result of a run started with start_run. While status is running there is no verdict: wait poll_after_s seconds and call again (a dry run takes about 60-120 s). Once it has finished, the result is exactly dry_run's, with its run_id: act on status and the verdict as for dry_run. An unknown run_id is status error. 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": {
      "run_id": "<run_id>"
    },
    "name": "get_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

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 richly: it discloses polling cadence, expected 60-120s runtime, that unknown run_id yields status error, that INCONCLUSIVE means stop and not retry, that errors indicate setup problems not change quality, and even platform requirements (Linux/WSL2, Docker, containerlab, no macOS/sandbox).

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

Conciseness3/5

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

Purpose is front-loaded, but the text sprawls into usage warnings and repeats the 60-120s timing twice ('60-120 s' and '60–120 s'), mixing polling guidance, platform requirements, and policy admonitions into one dense block without clear separation.

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?

An output schema exists so return values need no detailing, and the description still covers error/inconclusive states, polling behavior, and prerequisites thoroughly. An agent has everything needed to call and interpret it.

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?

Only one parameter (run_id) at 0% schema coverage, so the schema explains nothing. The description implies run_id originates from start_run and that an unknown value returns status error, but never states the run_id format or source explicitly, leaving a modest gap.

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 clearly it returns 'the result of a run started with start_run' and ties it to the dry_run workflow, so the resource (a run result) and relationship to start_run/dry_run are evident. It does not sharply delineate a single verb but the getter role is unambiguous.

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?

Explicitly says when to poll ('while status is running... wait poll_after_s seconds and call again'), when to use the workflow ('before proposing or applying any routing or policy change'), and rules out alternatives ('Ping is not a test'). It names sibling tools (record_baseline, verify_change) with conditions for using them.

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