Skip to main content
Glama
Sign In

AgentBIT

by app.agentbit
OverviewDiscussionsAdmin

URL Encode

agentbit.encode_url
Read-onlyIdempotent

RFC 3986 percent-encode an input string for safe use in URLs, query strings and path segments (spaces become %20). Pay-per-call via x402 (USDC, Base).

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": {
      "input": "<input>"
    },
    "name": "agentbit.encode_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
_paymentNoOptional base64 x402 PAYMENT-SIGNATURE payload. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent behavior, and the description adds important context beyond that: this is a pay-per-call operation via x402 with USDC on Base. The encoding behavior (spaces become %20) is also disclosed, which helps an agent predict the transformation.

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 sentences with no redundant wording. The first sentence front-loads the core functionality and encoding standard; the second covers the payment model. Every clause is informative.

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 simple stateless transformation tool, the description plus schema provides enough context: what to encode, where it is safe, and how payment works. There is no output schema, but the output for a percent-encoding tool is self-evident. Minor missing detail like exact encoding of non-ASCII characters would be nice but is not critical.

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 input parameter has no schema description, but the description supplies its meaning by referring to 'an input string' to percent-encode. The _payment parameter is explained in the schema itself, including the 'omit to receive payment requirements' behavior. Together, the description and schema cover both parameters' semantics.

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 states a specific verb and resource: 'RFC 3986 percent-encode an input string for safe use in URLs, query strings and path segments.' It clearly distinguishes this from sibling encoders and decoders by specifying the exact encoding standard and use cases. The added detail about spaces becoming %20 reinforces the tool's identity.

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?

The description gives clear when-to-use context: encoding strings for URLs, query strings, and path segments. It does not explicitly name alternatives or exclude cases like base64 or hex encoding, but the RFC 3986 framing makes the intended domain obvious to an agent.

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

All AgentBIT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources