Skip to main content
Glama

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

URL encode: percent-encode text for use in a URL

url_encode
Read-only

Percent-encode text for use in a URL query value (encodeURIComponent) and as a full URL (encodeURI). Use when building query strings. Example: text=a b&c=d/é. 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_encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to encode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: pricing at $0.01/call, first 25 free, failed calls free, and an explicit note that repeats are not free, which explains the otherwise puzzling idempotentHint=false. It stops short of describing the return shape (a plain encoded string), which is the one remaining gap.

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 capability and the encodeURIComponent/encodeURI distinction are front-loaded, and the pricing sentence earns its place because the tool is metered per call. The parenthetical pricing details make the middle of the text dense, but nothing is truly wasted.

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 one-parameter tool with no output schema, the definition covers what to pass in, when it applies, and what it costs. The only substantive omission is any statement of the return value or of the space-encoding convention, which matters for a percent-encoder.

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 exactly one parameter at 100% schema description coverage, so the baseline is 3. The example input "text=a b&c=d/é" does hint at which characters are in scope (spaces, ampersands, slashes, non-ASCII), but it is input-only and never says whether a space becomes %20 or +, so it doesn't materially resolve encoding semantics.

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 states a specific verb and resource (percent-encode text) and goes further by naming the two encoding modes it supports: encodeURIComponent for query values and encodeURI for full URLs. That is enough for an agent to tell it apart from a name like url_decode or url_parse, though it never explicitly names the decode counterpart as the inverse operation.

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?

"Use when building query strings" gives one concrete context, but the description offers no exclusions and no routing to alternatives (e.g., it never says to use url_decode to reverse this or url_parse when you need components rather than an opaque string). The two modes are mentioned but the description doesn't say which mode to choose when, leaving that inference to the agent.

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.