Skip to main content
Glama

Lazynext AI Slop Checker

list_rules

List the full pattern corpus (categories + every rule with id, severity, kind, match, fix). Use this to know what the scanner flags.

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 observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the returned payload structure (categories plus per-rule fields), which is real value given there is no output schema, but it says nothing about whether the corpus is static, how large it is, or whether results are cached or paginated. 'List' plus an empty schema implies a harmless read, yet the description never states that explicitly.

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 tight sentences: the first front-loads what is returned, the second front-loads why it matters. No filler, no restating of the tool 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 zero-argument listing tool with no output schema, enumerating the rule fields in prose covers the main gap an agent would face. A brief note on corpus size or on using it before the scan_* tools would make it fully self-sufficient.

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?

With zero parameters there is nothing to disambiguate, so the baseline applies. The description sensibly spends its words on the return shape instead of inventing parameter detail.

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 a specific verb ('List') and resource ('the full pattern corpus') and then enumerates exactly what each rule contains (id, severity, kind, match, fix). An agent knows precisely what comes back. It falls short of a 5 only because it never explicitly contrasts itself with the scan_* siblings, though the closing clause hints at that relationship.

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 to know what the scanner flags' supplies one concrete use case, tying the tool to the scanning workflow. However, it offers no when-not guidance, no prerequisites, and does not name scan_html/scan_text/scan_project as the follow-on actions, leaving the agent to infer the rest.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.