Skip to main content
Glama
Sign In
n8n-guard

n8n-guard

by flow-84
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Stuck executions

stuck_executions

Identify n8n executions stuck in the running state by comparing runtime to a threshold or workflow median, revealing abnormal runs that simple status listing misses.

Instructions

Executions sitting in running past a threshold or far past their own workflow's median runtime. Listing by status is not detection: this compares against a baseline.

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

Input Schema

NameRequiredDescriptionDefault
threshold_minutesNoMinutes a run may stay in `running` before it counts as stuck. Defaults to N8N_GUARD_STUCK_MINUTES.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the detection algorithm (fixed threshold or median-runtime baseline), which is real behavioral context beyond the schema, but it never states that the operation is read-only, what a result contains, or whether a baseline can be missing for new workflows.

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?

Two compact sentences, both front-loaded with the highest-value information: first what gets detected, then why it differs from a status listing. No filler or restatement of the name.

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?

For a one-parameter, no-annotation, no-output-schema tool, the description covers the detection logic well enough to call it correctly. The remaining gaps are minor: the shape of the results and the read-only nature are unstated, though both are strongly implied by the name and context.

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 coverage is 100%, so `threshold_minutes` and its environment-variable default are already documented in the schema. The description only alludes to 'a threshold' without adding semantics such as how it interacts with the median-runtime branch, so it adds little beyond structured data.

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 description names the resource (executions stuck in `running`) and gives the two concrete detection criteria: exceeding a threshold, or exceeding the workflow's median runtime. It also pre-empts confusion with a status-based listing. It lacks a clean leading verb (e.g., 'Find' or 'List'), so it reads as a fragment rather than a fully formed statement of action.

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?

The line 'Listing by status is not detection: this compares against a baseline' implicitly tells the agent to prefer this tool over a naive status filter. However, it does not state when the tool should not be used, nor does it name a sibling as the alternative, leaving the routing guidance 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

Other Tools