Skip to main content
Glama

URL encode/decode

bursia_url_encode
Read-onlyIdempotent

Percent-encode a text for use in URLs, or decode a percent-encoded string. Returns the converted text. Pure computation, free.

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

Input Schema

NameRequiredDescriptionDefault
modeNoencode (default) or decode.
textYesText to percent-encode, or an encoded string to decode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / mode / description
      Added value: +"encode (default) or decode."
    • addedInput schema / properties / mode / enum
      Added value: +[
      +  "encode",
      +  "decode"
      +]
    • addedInput schema / properties / text / description
      Added value: +"Text to percent-encode, or an encoded string to decode."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description still adds two things beyond them: the return value ('Returns the converted text', valuable because there is no output schema) and the cost/effort profile ('Pure computation, free'). It does not say what happens on malformed percent sequences during decode.

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?

Two short sentences, front-loaded with the action, no filler. Nothing could be removed without losing information.

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 two-parameter, annotation-covered, no-output-schema utility this is nearly complete — the return value and cost are stated up front. The only missing piece is error behavior on invalid encoded input, which matters for the decode path.

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% and the mode enum documents both values plus the default, so the schema already does the work. The description only restates the two directions and adds no format or escaping details (e.g. whether space becomes %20 or +), so baseline 3 applies.

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 names both specific operations (percent-encode / percent-decode) and the resource (text for URLs), so an agent can tell it is a converter rather than a parser or escape utility. It does not differentiate itself from near neighbors like bursia_url_parse or bursia_html_escape, which is the only visible gap.

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 by 'for use in URLs', but there is no explicit when-to-use or when-not statement and no named alternative (e.g. url_parse for breaking a URL apart, html_escape for HTML contexts). An agent must infer the boundary from the sibling list.

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