Skip to main content
Glama

Generate a rewrite of a text in another tone

text_paraphrase
Read-only

Rewrite a text in a chosen tone (neutral, formal, casual, simple, persuasive) and length (shorter, same, longer), keeping its meaning and language. Up to 3 variants. Workers AI (Llama 3.3 70B) writes the rewrite; only the rewritten text is returned. Up to 8,000 characters. The model can change nuance, so read the result. Related tools on this server, for a different need: text_chunk when you need to generate overlapping text chunks with character offsets; text_faq when you need to generate FAQ pairs grounded in a text with checked quotes. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to rewrite, up to 8,000 characters (JSON body field)
toneNoneutral (default), formal, casual, simple or persuasive
lengthNosame (default), shorter or longer
variantsNoHow many rewrites, 1 to 3, default 1

Output Schema

NameRequiredDescriptionDefault
toneNo
countNo
modelNo
lengthNo
sourceNo
variantsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real substance: the backing model (Llama 3.3 70B), the 8,000-character ceiling, that only the rewritten text is returned, and that failed calls are not billed. Pricing is disclosed clearly ($0.003 per successful call, x402 on Base/Solana and other networks). What it omits is latency/rate-limit behavior, which keeps it from 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?

Purpose is front-loaded in the first clause, then parameters, then caveats, then alternative routing, then price – a sensible order with no filler. The pricing sentence is long and carries network detail that could be trimmed, but every sentence still conveys usable information.

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?

An output schema exists, so the return-value burden is light, and the description still flags that only the rewritten text comes back. For a four-parameter, read-only generative tool the coverage is essentially complete; only cost-relevant operational details like rate limits or turnaround are absent.

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?

Schema coverage is 100% and each of the four parameters already carries a description with defaults, so the schema does most of the work. The description restates the tone options and the shorter/same/longer choices and repeats the 8,000-character limit without adding syntax or interaction details (e.g., how variants differ from one another). Baseline 3 is appropriate.

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 and resource ("Rewrite a text") plus the controllable dimensions (tone, length, variant count) and explicitly names the sibling tools text_chunk and text_faq as serving different needs, so an agent can tell it apart without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule for the closest alternatives: use text_chunk for overlapping chunks with character offsets, text_faq for grounded FAQ pairs with checked quotes. It also sets the verification expectation ("The model can change nuance, so read the result"), which is exactly the guidance needed before applying a rewrite.

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