Skip to main content
Glama

Agent Bits

by dev.agentbits

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.1/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It adds context about when decoding is appropriate but does not discuss edge cases, error handling, or potential side effects (e.g., whether plus signs are decoded). Since the core behavior is straightforward, the description is adequate but not exhaustive.

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-structured with bullets, but the 'Use when' bullets repeat the same idea as the opening sentence. A tighter version could remove redundancy while remaining helpful.

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-parameter decode tool with no output schema, the description provides sufficient context on purpose and usage, and mentions alternatives. However, it omits explicit parameter mapping and edge-case behavior. Overall, it is mostly complete for a simple 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?

The input schema defines only 'value' with no description, and the description does not explicitly map this parameter to the encoded string. It implies the input via the tool's purpose but lacks a direct statement like 'Pass the percent-encoded string in the value parameter.' Schema coverage is 0%, so the description should compensate more.

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 'Decode a percent-encoded URL component into plain text', specifying a verb and resource, and differentiates from sibling encoders/decoders 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?

Provides explicit 'Use when' and 'Do not use when' sections with named alternatives (url_encode, base64_decode), giving clear guidance on appropriate usage.

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.1/5.0
Disambiguation5/5

Each tool targets a distinct data format and operation, with explicit 'Do not use when' cross-references to prevent confusion. For example, base64_encode/decode, url_encode/decode, and timestamp_convert/timezone_convert are clearly separated, and the various validators (ISBN, Luhn, UUID, JSON) apply to different identifiers.

Naming Consistency4/5

Most tool names follow an object_operation pattern (e.g., base64_decode, country_lookup, timestamp_convert), using lowercase with underscores. The main deviation is countries_bulk, which uses a noun+adjective form without an explicit operation, making it inconsistent with the verb-like operations used elsewhere.

Tool Count3/5

With 18 tools, the server falls into the 16-25 range which feels heavy for a utility collection. While each tool is individually useful and the scope is broad, the count is higher than typical for a well-focused server and may overwhelm agents scanning the available options.

Completeness4/5

The set provides solid coverage of encoding/decoding, validation, lookups, and conversions, with paired encode/decode and convert functions. However, some common utilities such as hashing, HTML entity encoding, UUID generation, or email validation are absent, leaving minor gaps for agents that need those operations.

Resources