Skip to main content
Glama

dislop

dislop_deslop

Self-healing LLM anti-slop rewrite: pre-check -> plain rewrite -> deterministic/3rd-order/numeric gate -> auto-repair (2 credits, 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_deslop"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
packNo
textYes
filenameNo
modalityNo
voiceProfileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add genuinely useful facts: a 2-credit cost and a required Bearer dslp_* token. It omits failure behavior (what happens if the numeric gate or auto-repair fails), whether the rewrite is lossy, and any latency or rate-limit expectations.

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 front-loaded sentence with arrow notation that conveys the pipeline compactly and wastes few words. It is dense but well ordered, though some terms ('3rd-order', 'numeric gate') are opaque without further definition.

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 tool with no annotations, no output schema, six undocumented parameters, and a nested object, this description is too thin. Cost and auth are covered, but the parameter surface — the main thing an agent must get right to call it — is entirely unexplained.

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

Parameters1/5

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

Six parameters at 0% schema description coverage, including three enums (lang, pack, modality) and a nested voiceProfile object, and the description says nothing about any of them. An agent cannot know what a 'pack' selects, what modality values mean, or what voiceProfile should contain.

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 combo ('anti-slop rewrite') and outlines the pipeline (pre-check -> rewrite -> gate -> auto-repair), which distinguishes it from read-only siblings like dislop_check and dislop_review. It stops short of naming an alternative explicitly, and 'slop' is left undefined.

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 statement of when to reach for this versus dislop_check, dislop_review, or dislop_explain. The pipeline stages imply this is the full correction path, but the agent must infer that rather than being told.

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.