Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

URL decode: decode percent-encoded URL text

url_decode
Read-only

Decode percent-encoded text, treating + as a space when plus=true (form encoding). Use to read encoded links and form data. Example: text=a%20b%26c. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not 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": "url_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
plusNotrue to read + as space
textYesThe encoded text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses cost ($0.01/call via x402 USDC or card key), a 25-call free tier, that failed calls are free, and that repeated calls are billed again. That last point explains why idempotentHint is false for what is otherwise a pure computation, which the annotations alone would leave confusing.

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 purpose and the '+' semantics are front-loaded in the first sentence, followed by usage, an example, and pricing. Every sentence carries information, though the billing sentence is dense enough that it slightly crowds the definition.

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, non-destructive transformation with full schema coverage and no output schema, the definition covers purpose, when to use, cost, and side-effect profile. It does not mention the return format or how malformed percent sequences are handled, which is the remaining gap.

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?

Schema coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds the form-encoding framing for plus=true and a concrete input example (text=a%20b%26c), giving a modest but real boost over the schema text.

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 opens with a specific verb+resource: 'Decode percent-encoded text,' and adds a scope qualifier about '+' handling under plus=true. The decode-vs-encode distinction is implicit in the verb, so an agent can separate it from url_encode, but no sibling is named explicitly.

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

Usage Guidelines4/5

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

'Use to read encoded links and form data' gives a clear when-to-use context tied to concrete scenarios. It stops short of exclusions or naming alternatives (e.g., url_parse for structural parsing), so it falls short of full routing guidance.

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.