Skip to main content
Glama

Lazynext AI Slop Checker

rewrite_text

Apply conservative safe rewrites (whole-word synonym swaps and phrase deletions only) to a text. Returns the rewritten text plus the change list.

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

Input Schema

NameRequiredDescriptionDefault
textYestext to rewrite

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?

No annotations are supplied, so the description carries the full burden and does reasonably well: it defines the exact transformation class (whole-word swaps and deletions only, nothing generative or paraphrastic) and states that the result is returned as text plus a change list rather than applied in place. It does not cover limits, ordering of changes, or failure behavior, which keeps it short of a 5.

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 short sentences with zero filler: the transformation constraint is front-loaded and the return behavior follows. Nothing is repeated from the title or schema.

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 single-parameter text transformation with no output schema, the description covers both the transformation rules and the shape of the return value (rewritten text plus change list), which is enough to call it correctly. The structure of the change list entries is left unspecified, a minor gap.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents it and the baseline is 3. The description adds no meaning about the input beyond what the schema's 'text to rewrite' provides.

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 states a specific verb and resource ('Apply conservative safe rewrites ... to a text') and goes further by naming the exact operations performed (whole-word synonym swaps, phrase deletions). That mechanism detail makes it clearly distinct from the scan_*/judge siblings, 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 by the word 'conservative' and the restriction to synonym swaps and deletions, which suggests when the output is acceptable. There is no explicit when-to-use, when-not-to-use, or statement about which sibling to prefer for detection vs. rewriting.

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.