Skip to main content
Glama

remove_watermark

Remove the statistical AI-text watermark by re-generating every token. Returns clean text plus before/after scores.

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

Input Schema

NameRequiredDescriptionDefault
modeNoparaphrase
textYesThe AI-generated passage to clean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose two important traits: the text is fully regenerated (so content/wording will change, not merely be flagged) and the response includes before/after scores. It omits what an agent needs for a mutation-adjacent operation with no annotations: whether meaning can drift, length or rate limits, failure behavior, and which mode is appropriate.

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 tight sentences with zero waste: the action and mechanism come first, followed by the return shape. Nothing is padded or restated from the title.

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

Completeness3/5

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

Because there is no output schema, it is good that the description names the return values (clean text plus before/after scores). However, with no annotations and an undocumented mode parameter, the definition leaves the agent guessing about the single most consequential choice the tool exposes.

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 coverage is 50%: the text parameter is documented in the schema, but the mode enum (paraphrase/backtranslate) has no description anywhere. The description never mentions mode or how choosing paraphrase versus backtranslate affects the result, so it adds no meaning beyond the schema's bare enum values.

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 outcome ("Remove the statistical AI-text watermark") plus the mechanism ("re-generating every token"), which tells an agent exactly what will happen to the text. It does not explicitly contrast itself with the sibling check_score, but the purpose is unambiguous on its own.

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: the agent must infer that this is the tool to call when text has been flagged as AI-generated. There is no explicit when-to-use statement, no mention of pairing with check_score to verify the result, and no note on when this tool is inappropriate.

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.

Resources