Skip to main content
Glama
MCP Toolkit

MCP Toolkit

url_encode

Percent-encode or decode URL components to safely handle special characters in links, query strings, and API requests.

Instructions

Percent-encode or decode a URL component.

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>",
      "operation": "<operation>"
    },
    "name": "url_encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely drops it. It does not say what happens on decode of malformed percent-escapes, whether the operation is reversible, how spaces are handled (%20 vs +), or whether non-ASCII input is UTF-8 encoded.

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?

A single front-loaded sentence with zero filler — the operation and target are stated immediately. It is efficient, though its brevity contributes to the specification gaps scored elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter utility with no output schema, the description is just barely enough to attempt a call. Missing details about decode failure behavior and space/Unicode handling are realistic gaps given the no-annotation, zero-coverage schema.

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?

Schema description coverage is 0%, and the description fails to compensate: 'text' is never explained (is it the raw component, a full URL, or arbitrary text?), and the encode/decode enum in the schema is the only place the operation values appear. The word 'component' is the sole hint that full URLs may not be accepted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific pair of verbs (percent-encode / decode) applied to a specific resource (a URL component), so an agent immediately knows the transformation performed. It stops short of naming a sibling such as base64_convert to clarify why you would pick this encoder over that one.

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?

There is no guidance on when to use this versus base64_convert or url_inspect, and no statement about prerequisites or exclusions. The agent must infer usage entirely from the name and the two-sentence-free description.

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