Skip to main content
Glama

Agent Bits

by io.github.rwaldman

url_decode

Decode a percent-encoded URL component into plain text when reading query parameters, path segments, or form values that contain escaped characters.

Use when:

  • Decode this percent-encoded URL component

  • Convert %20-style escapes back to plain text

  • Recover the original string from an encoded query parameter

Do not use when:

  • Percent-encode text for a URL (use url_encode)

  • Decode Base64 payloads (use base64_decode)

  • Parse HTML entities that are not URL percent-encoding

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It explains the main behavior and typical use cases, but does not disclose edge cases such as handling of invalid percent-encoding or whether '+' is decoded as a space. This is adequate but not deeply transparent.

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 well-organized with a main sentence and bullet-style sections. It is concise, though the 'Use when' bullet 'Decode this percent-encoded URL component' is slightly redundant with the first sentence.

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

Completeness5/5

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

For a simple one-parameter decoder, the description is complete: it states the transformation, provides concrete use cases, and explicitly lists exclusions. No output schema exists, but the plain-text result is clearly stated.

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

Parameters4/5

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

The schema only defines a string parameter named 'value' with no description. The tool description compensates by indicating that the value is the percent-encoded URL component to decode, adding practical meaning beyond the bare 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?

The description clearly states the tool decodes a percent-encoded URL component into plain text. It names the resource (URL component) and specific operations, and distinguishes itself from siblings like url_encode and base64_decode.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit 'Use when' and 'Do not use when' sections, including named alternatives (url_encode, base64_decode) and clarifies contexts like reading query parameters and path segments. This gives clear guidance on when to select this tool.

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

All Agent Bits toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear use cases and explicit 'Do not use when' guidance preventing confusion. For example, base64_decode and url_decode handle different encoding schemes, while timestamp_convert and timezone_convert address separate time operations.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern (e.g., base64_decode, country_lookup, uuid_validate). While verbs vary (decode, encode, lookup, validate, convert), the naming format is uniform and predictable.

Tool Count4/5

The 18-tool set is slightly above the typical 3-15 range, but the breadth is justified by the server's purpose as a general-purpose utility toolkit. Each tool earns its place, and the count does not feel overwhelming or redundant.

Completeness4/5

The toolkit covers encoding/decoding, validation, lookups, and conversions across common developer needs. Minor gaps exist, such as no UUID generation tool to complement uuid_validate, and no HTML entity encoding/decoding, but these are not critical omissions for the stated utility scope.

Resources