Skip to main content
Glama

dislop

dislop_check

Deterministic anti-slop check for AI artifacts, clichés, 2nd-order slogans, and AI UI templates (0 credits, no login required).

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

Input Schema

NameRequiredDescriptionDefault
packNo
textYes
filenameNo
modalityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It usefully discloses that the check is deterministic (reproducible, rule-based rather than model-judged) and free without login, but it says nothing about the result shape, severity levels, or whether the operation is purely read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the core purpose front-loaded and no filler; the parenthetical cost/auth clause is the only addition. It is compact, though the density of jargon ('2nd-order slogans') costs some immediate clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter tool with zero schema coverage, no annotations, and no output schema, the definition is too thin: it never explains the pack presets, the modality/filename parameters, or what the agent receives back. The agent can guess it passes text through but cannot confidently choose a pack or interpret results.

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 0% on four parameters, so the description should compensate. It conveys the domain of 'text' and the slop categories generally, but adds no meaning for 'pack' (whose enum values like 'core' and 'business-brief' are opaque), 'modality', or 'filename'.

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 concrete verb and target: a deterministic check for AI slop patterns, clichés, second-order slogans, and AI UI templates. An agent can tell this is a detection pass rather than a rewrite or review pass, though it never explicitly names how it differs from dislop_review or dislop_deslop.

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?

The only usage context is the cost/auth note (0 credits, no login required). There is no guidance on when to pick this over dislop_review, dislop_deslop, or dislop_explain, and no preconditions on input type or size.

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.