n8n-guard

Full guard run

guard_run

Run all n8n operational health checks in one resilient sweep that retries failing steps, reports partial findings, and continues remaining checks for scheduled monitoring.

Instructions

Runs every check in one resilient sweep. Individual steps retry and, if they still fail, are reported as findings while the remaining checks finish. Use this for scheduled monitoring.

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

Input Schema

Name	Required	Description	Default
`keep_days`	No	Retention window used by the retention step. Defaults to 30.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

B3.4/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 valuable failure semantics: steps retry, persistent failures surface as findings, and remaining checks still complete. However, it never says whether the run is read-only or mutating — notable given a retention step governed by keep_days likely deletes data — nor does it mention runtime, cost, or permissions.

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?

Three short sentences, front-loaded with the core action and followed by failure behavior and usage. Nothing is redundant, though the definition is thin enough that it could have spent a few more words on the mutation/retention aspect without bloat.

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?

For an aggregate sweep with no output schema, the description adequately covers what happens and how partial failures are handled. It is still incomplete on whether the run mutates data (the retention step), what findings look like, and how long a full sweep takes.

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?

Schema description coverage is 100% and the single keep_days parameter is fully documented with a default and exclusivity bound in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 a specific verb and scope: it runs every check in one sweep, which implicitly contrasts with the granular siblings (db_health, git_drift, retention_report, stuck_executions). It does not name which checks are included or name the siblings it aggregates, so an agent must infer the coverage set.

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

Usage Guidelines3/5

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

"Use this for scheduled monitoring" gives one clear positive usage context. There are no exclusions or explicit pointers to the per-check siblings for targeted, ad-hoc queries, leaving the choice between aggregate and single-check tools to inference.

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

Deploy Server