Skip to main content
Glama

dislop

dislop_review

Hybrid deterministic + 3rd-order structural + LLM anti-slop review (1 credit, requires Bearer dslp_* token).

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_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
packNo
textYes
filenameNo
modalityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/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 add two genuinely useful behavioral facts – cost (1 credit) and required auth (Bearer dslp_* token) – which go beyond the schema. However, it never states whether the operation is read-only or mutating, what the review returns, how long it takes, or what happens on insufficient credits, leaving the mutation/safety profile entirely undisclosed for a paid LLM-backed call.

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 dense sentence with no filler; the cost and auth caveat are correctly parenthesized rather than buried. Its compactness is achieved by stacking unexplained jargon, but on raw size and structure it wastes nothing.

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 five-parameter, paid, LLM-backed tool with zero annotation coverage, no output schema and no parameter documentation, the definition is severely under-specified. An agent cannot reliably select the right pack or modality, nor predict what it gets back, from this description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, three of which are enums (lang, pack, modality) with enumerated values that are not explained. The description mentions none of them – it does not say that packs are quality profiles, that modality should match the input format, or that filename is optional metadata – so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb-ish action ("anti-slop review") and hints at the mechanism ("hybrid deterministic + 3rd-order structural + LLM"), so an agent can tell it evaluates text quality rather than mutating it. But the phrasing is jargon-heavy, and with siblings dislop_check, dislop_deslop, dislop_explain and dislop_voice_extract present, the description does nothing to say how "review" differs from "check" or "deslop" – exactly the distinction an agent must make.

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 when-to-use guidance at all: no precondition, no exclusion, no named alternative. The agent must guess whether this replaces dislop_check or complements it, and nothing states what input is appropriate or which pack/modality combination to pick.

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.