Skip to main content
Glama

url_encode

Read-onlyIdempotent

Encodes text into percent-encoded format to safely include it in query strings and URLs.

Instructions

URL-encode text (percent-encoding for query strings).

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

Input Schema

NameRequiredDescriptionDefault
textYesText to URL-encode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety and repeatability are covered structurally. The description adds only that percent-encoding is used; it does not say how spaces or reserved characters are handled, which is the one behavior an agent might still care about.

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?

One short sentence, front-loaded with the action and resource, with the qualifier in parentheses. Nothing is wasted or buried.

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 single-argument pure transformation with full annotation coverage and a documented parameter, the definition is sufficient to call the tool correctly. The only residual gap is encoding specifics such as space handling, which is minor for this class of utility.

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?

There is a single parameter with 100% schema description coverage ('Text to URL-encode.'), so the schema carries the load and the baseline of 3 applies. The description adds no format or example detail beyond the schema.

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?

States a specific verb and resource ('URL-encode text') and the parenthetical 'percent-encoding for query strings' disambiguates which encoding scheme is applied. It does not name the sibling url_decode, but the name/description pair is self-distinguishing.

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?

The phrase 'for query strings' hints at intended context but there is no explicit when-to-use, no when-not, and no reference to url_decode or base64_encode as alternatives. An agent must infer usage from the name alone.

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

Deploy Server

Other Tools