Skip to main content
Glama

Text rewrite

text_rewrite
Read-onlyIdempotent

AI text rewrite & paraphrase in professional, concise, casual, technical, executive, plain, friendly, or formal tone while preserving facts & numbers (Llama 3.1 8B Fast). $0.001 per call over x402 or X-API-Key. Call once without payment for terms, then call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
textYesSource text to rewrite (10 to 12000 characters).
toneNoTarget tone (default: professional).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
instructionsNoOptional extra rewrite instructions (up to 300 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, idempotent, open-world), and the description adds meaningful context beyond them: per-call pricing ($0.001), the auth mechanisms (x402 or X-API-Key), the underlying model (Llama 3.1 8B Fast), and the two-step payment handshake. That is exactly the kind of cost/auth/behavior context the annotations cannot express. It does not describe latency, error modes, or what the response looks like, 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.

Conciseness4/5

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

Front-loaded with the capability statement, then a compact sentence carrying pricing, auth, and the payment flow. The tone enumeration duplicates the schema enum and the model-name parenthetical is marginal, but nothing is genuinely wasteful.

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?

With 4 fully documented parameters and no output schema, the description supplies the operationally critical extras (cost, auth, payment handshake, factual preservation). Return-value shape is the main omission, but for a straightforward rewrite tool with complete parameter docs that is a minor gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns more by explaining the `payment` parameter's protocol semantics — that omitting it returns terms and that it is a signed x402 payload. It also implicitly frames `text` and `tone` via the preservation invariant and tone list. `instructions` is never mentioned in the description, though the schema documents it adequately.

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

Purpose5/5

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

States a specific verb pair (rewrite & paraphrase), the resource (text), the transformation dimension (tone, with the enum values listed), and a key invariant (preserving facts & numbers). This is enough for an agent to distinguish it from siblings like text_summarize, text_translate, or text_classify without opening any schema.

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?

The description gives one concrete usage rule: call once without `payment` to obtain terms, then call again with `payment`. That is genuinely actionable. However, it offers no guidance on when to choose this tool over the other text-processing siblings, and no exclusions or prerequisites beyond payment.

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