Skip to main content
Glama

Rewrite Text

neuron_rewrite_text

Rewrite or transform text with AI based on your instructions, such as making it more formal, translating, or summarizing.

Instructions

Use AI to rewrite or transform text based on an optional instruction (e.g., make it more formal, translate, summarize)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to rewrite
instructionNoInstructions for how to rewrite the text (e.g., 'make it more professional', 'translate to Spanish')
Behavior2/5

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

No annotations are provided, so the description must cover behavioral aspects. It only states 'Use AI', which is vague. It does not disclose model specifics, rate limits, cost, or whether the original text is preserved. The description adds minimal behavioral context beyond the basic operation.

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 clear sentence with no unnecessary words. It front-loads the core purpose and provides an example, making it efficient and easy to parse.

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 there is no output schema, the description should at least hint at what the tool returns (e.g., the rewritten text). It does not mention the output format or any side effects, leaving a significant gap in completeness.

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%, so the schema already describes both parameters. The description provides example instructions that add slight additional context, but does not significantly enhance understanding beyond the schema. 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?

The description clearly states the tool's function: to rewrite or transform text using AI, with an optional instruction. It provides concrete examples (make more formal, translate, summarize) that solidify understanding. This is specific and distinct from other tools in the list.

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 implies when to use the tool (rewriting text), but lacks explicit guidance on when not to use it or comparison to similar tools. There are no directly similar sibling tools, so this is not critical, but still missing explicit usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conquext/neuron-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server