TextToolkit

Overview Schema Source Related Servers Discussions Admin

encode_url

Encode text for URLs by converting special characters to percent-encoded format, ensuring safe transmission in web addresses.

Instructions

Encode text for URLs

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

Input Schema

Name	Required	Description	Default
`text`	Yes	The text to encode or decode

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description minimally conveys URL encoding but lacks specifics on character handling or behavior for invalid input. It is adequate but not detailed.

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?

Single sentence, immediately front-loads the action and target. No unnecessary words.

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?

For a simple encoding tool with one parameter, the description is mostly complete. It could clarify the encoding scheme (e.g., percent encoding) but is sufficient given sibling context.

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 does not add extra meaning beyond the schema, which already has 100% coverage. The schema's parameter description (encode or decode) is broader than the tool's purpose, but this is not addressed in the tool description.

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 'Encode text for URLs' clearly states the action (encode) and the target resource (text for URLs), distinguishing it from siblings like decode_url and other encoding tools.

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?

No guidance on when to use this tool versus alternatives such as decode_url, encode_base64, or other string transformation tools.

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