Underground Cultural District MCP Server

encode-url

Encode or decode text using percent-encoding for URL-safe transmission. Supports both encode and decode modes.

Instructions

URL-encode or URL-decode a string.

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	Text to process
`mode`	No		encode

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.1.0Apr 17, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'URL-encode or URL-decode a string' without detailing the encoding scheme, special character handling, or any side effects, making it insufficient for informed invocation.

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?

The description is a single concise sentence that gets straight to the point. However, it could be slightly more informative without losing brevity, such as mentioning typical use cases.

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 simplicity of the tool (2 parameters, no output schema), the description is minimally complete but lacks essential details about expected input format, output type, and edge cases, which are needed for confident invocation.

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

Parameters2/5

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

The input schema has 50% coverage (only 'text' has a description). The description adds no additional meaning about the parameters beyond what the schema provides, failing to compensate for the missing parameter descriptions for 'mode'.

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 that the tool performs URL encoding or decoding on a string, which is specific and distinguishes it from siblings like encode-base64 or decode-base64. The verb-process and resource are well-defined.

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 is provided on when to use this tool versus alternatives (e.g., other encoding tools) or any prerequisites. The description only states what it does, leaving the AI agent to infer usage context.

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