Skip to main content
Glama

URL Encode / Decode API - percent-encoding

url_encode_decode
Read-onlyIdempotent

Percent-encode or decode text and URLs (whole link or single value, + as space). Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/url-encode-decode.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "encode",
      "text": "https://example.com/a b?x=ü",
      "wholeLink": true
    },
    "name": "url_encode_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoencode or decodeencode
textYesThe text
wholeLinkNoKeep : / ? & = as they are (mode=encode)
plusIsSpaceNoTreat + as space (mode=decode)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds genuinely non-obvious context: processing happens server-side, files are deleted immediately with nothing stored, and there are concrete limits (25 calls/day free per IP, $0.001/call via x402). These cost and privacy facts materially affect whether and how an agent should call it; only the response/return shape is left unaddressed.

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?

Two sentences, front-loaded with the core capability, then the operational facts. Dense but no filler; the pricing/URL tail is slightly promotional yet carries real behavioral information an agent needs.

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 four-parameter transform tool with full schema coverage, no output schema and strong annotations, the description supplies the operational essentials (statelessness, limits, cost). Only the return-value shape is unmentioned, which is a minor gap given the operation's obvious output.

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 description coverage is 100%, so the schema already documents mode, text, wholeLink and plusIsSpace. The description restates the meaning of '+' as space and the whole-link distinction, adding marginal clarity but nothing about syntax, formats, or edge cases beyond the schema.

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: 'Percent-encode or decode text and URLs.' Naming the exact encoding scheme (percent-encoding, with + as space) distinguishes it from the sibling base64_encode_decode, and the parenthetical clarifies it handles both whole links and single values.

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?

Usage is implied through the 'whole link or single value' phrasing and the mode/flag hints, which tell an agent what shapes of input are supported. However, there is no explicit when-to-use vs when-not guidance and no alternative tool is named, so the agent must infer selection.

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