Skip to main content
Glama

Lazynext AI Slop Checker

scan_text

Scan plain text for AI-slop writing tells. Returns score (0-100), verdict, per-category breakdown, and every match with a fix suggestion.

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": {
      "text": "<text>"
    },
    "name": "scan_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesplain text to scan
profileNoseverity profile (default | strict | lenient)
rewriteNoinclude safe auto-rewrites (text only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description still conveys a scan-and-report operation and usefully discloses the score range, verdict, category breakdown, individual matches, and fix suggestions. It does not explicitly confirm that source text is never modified or explain score direction and verdict thresholds, leaving some behavioral interpretation to the agent.

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 front-load the purpose and then summarize the returned information. There is no filler, and the output details earn their place because no output schema is supplied.

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 simple three-parameter scanner with fully described inputs, this is sufficient for basic selection and invocation, and the output summary compensates for the missing output schema. Explicit alternative routing and clarification of score, verdict, and profile semantics would make it more 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 description coverage is 100%, so the schema already documents the text, severity profile enum, and rewrite flag. The description adds no further detail about how profiles change results or how rewrite affects the response, making the baseline score appropriate.

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 gives a specific verb, input resource, and detection target: scanning plain text for AI-slop writing tells. It clearly states the task but does not explicitly differentiate the tool from sibling scanners or rewrite_text.

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 plain-text scope and AI-slop detection goal imply when to use the tool, providing basic selection context. There is no explicit when-not guidance or routing for other input formats, project-wide scanning, or requests that require rewriting rather than diagnosis.

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.