Skip to main content
Glama

check_tools

Detect which external scanners Draugr can find and see what to install for missing ones. Run it before scans or after a failure, since absent scanners cause failed controls.

Instructions

Report which external scanners Draugr can find on this machine, and what to run if any are missing. Pass the path of the Saga descriptor to check only the tools a scan of it runs, the ones draugr doctor requires; without a path, every tool Draugr knows about is checked. Call this when a scan fails or before suggesting one: a control whose scanner is absent cannot run, and Draugr reports that as a failure rather than a pass. This only looks, it will not install anything.

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_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNopath to the Saga descriptor about to be scanned; without it, every tool Draugr knows about is checked, including ones this project never runs

Output Schema

NameRequiredDescriptionDefault
noteYes
readyYestrue when nothing required is missing
toolsYes
remedyNo
missingNorequired tools that are absent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.160.0
    • changedInput schema / properties / path / description
      Previous value: -"path to a Saga descriptor; without it, every tool Draugr knows about is checked"New value: +"path to the Saga descriptor about to be scanned; without it, every tool Draugr knows about is checked, including ones this project never runs"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description must define the safety profile. It does: "This only looks, it will not install anything" establishes a non-mutating, read-only operation. It also explains a non-obvious behavior, that missing scanners are reported as failures rather than skips, though it says nothing about how detection is performed or how costly it is.

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

Conciseness4/5

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

The description is dense and front-loaded, stating purpose first, then parameter modes, then usage triggers, and finally the read-only guarantee. The clause "the ones `draugr doctor` requires" is slightly awkward, but every sentence still contributes useful information.

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 is present, so the return format does not need to be explained. For a single optional parameter, the description covers both invocation modes and the failure semantics that motivate calling the tool. The only gap is detection mechanics and expected latency.

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 100%, so the single parameter is already documented. The description still adds meaning: with a path, only the tools a scan of that descriptor runs are checked; without a path, everything Draugr knows about, including tools this project never runs, is checked.

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 first sentence gives a specific verb and resource: report which external scanners Draugr can find on this machine. It also distinguishes the tool from siblings like `scan` and `validate_saga`, because the point is detection only, with no installation and no scanning.

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?

The description tells the agent exactly when to call this tool: when a scan fails, or before suggesting a scan. It also gives a supporting reason: a control whose scanner is absent is reported as a failure rather than a pass. It never names a concrete alternative such as `scan` or `validate_saga`, so it stops short of full when/when-not routing.

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