Skip to main content
Glama
Sign In
n8n-lint

n8n-lint

by shulkyn-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List lint rules

list_rules

Lists all available lint rules with IDs, names, severities, and descriptions so agents and reviewers can discover which workflow reliability checks n8n-lint supports.

Instructions

List all lint rules with id, name, severity and description.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only operation by saying 'List', but does not explicitly state read-only/safe behavior, auth requirements, rate limits, pagination, or ordering.

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?

A single front-loaded sentence that states the action, the resource, and the returned fields with no wasted words. It is appropriately sized for a simple list endpoint.

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 zero-parameter list tool with no output schema, the description helpfully lists the returned fields (id, name, severity, description). It is mostly complete, though it omits pagination, ordering, and any behavioral context that would help an agent use it confidently.

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 has zero parameters, so there is no parameter semantics to clarify and the baseline score is 4. The description appropriately focuses on the return fields instead.

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 states a specific verb ('List') and resource ('lint rules') and enumerates the returned fields. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools like explain_rule or lint_workflow.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus explain_rule or lint_workflow, nor any prerequisites, exclusions, or filtering context. The only implied usage comes from the word 'List', which is not enough to route among siblings.

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