Skip to main content
Glama

Lazynext AI Slop Checker

scan_project

Scan a local directory tree (prose/markup/styles/code lenses) and return a pooled report: score, top offending files, category breakdown. Local filesystem access only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dir": "<dir>"
    },
    "name": "scan_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirYespath to a directory
profileNoseverity profile (default | strict | lenient)
topFilesNohow many top files to report (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 does disclose the return contents (score, top offending files, category breakdown) and that access is local-filesystem only, which usefully rules out remote/URL inputs, but it says nothing about read-only guarantees, permissions, size/time limits, or failure behavior on unreadable paths.

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 dense sentence with the resource, the lenses, the returned report, and the access constraint, all front-loaded. Nothing is padding.

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?

With no output schema, the description correctly compensates by naming what the report contains (score, top files, category breakdown), and all three parameters are covered by the schema. Only the lack of any runtime/permission caveats for a filesystem-walking tool keeps it short of complete.

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 all three parameters are already documented with types, an enum, and defaults. The description only loosely links 'top offending files' to topFiles and the lenses to the scan; it adds no format or semantics beyond the schema, so the baseline 3 applies.

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 resource ('scan a local directory tree') and even enumerates the lenses (prose/markup/styles/code) plus the returned payload shape. The 'directory tree' scope implicitly separates it from the file-level siblings scan_html/scan_text, though no sibling is named explicitly.

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?

Usage is only implied: the directory-tree scope and 'local filesystem access only' hint at when this applies versus a single-file scan, but there is no explicit when-to-use/when-not statement or named alternative.

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.