Text-Transformer

reverse

reverse

Reverse the order of characters in text to create mirror versions or solve string manipulation tasks.

Instructions

Reverse the order of characters in text

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

Input Schema

Name	Required	Description	Default
`text`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 5, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the core transformation but lacks details on edge cases (e.g., handling of Unicode, whitespace, or empty strings), error conditions, or output format. This is a significant gap for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly and understand the core functionality.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the reversed text output looks like (e.g., string format), handle potential errors, or provide usage context relative to sibling tools. For a simple tool, it meets a bare minimum but leaves gaps in behavioral understanding.

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?

The description implies the 'text' parameter is the input to reverse, but with 0% schema description coverage and only one parameter, it adds minimal meaning beyond the schema's type definition. It doesn't specify constraints like length limits or character set handling, resulting in an adequate but basic level of parameter information.

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?

The description clearly states the specific action ('reverse the order of characters') and the resource ('text'), distinguishing it from sibling tools like capitalize or lowercase that perform different text transformations. It precisely defines what the tool does without being vague or tautological.

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?

The description provides no guidance on when to use this tool versus alternatives like isPalindrome or countCharacters, nor does it mention any prerequisites or exclusions. It states what the tool does but offers no context for selection among the available text manipulation tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server