Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_url

Read-onlyIdempotent

Percent-encode or decode text for URL-safe use, converting characters to percent-encoded format or restoring original characters.

Instructions

URL Percent-Encode and Decode. Percent-encode text into a URL-safe form or decode percent-encoded text back to its original characters, using encodeURIComponent / decodeURIComponent semantics (space becomes %20, reserved characters like &, =, ?, /, # are escaped). Use it for query-parameter values, path segments, and form data; use encoding_decoding_html_entities instead to escape characters for HTML markup, or encoding_punycode to convert international domain names to ASCII. Pure local string transformation — read-only, non-destructive, contacts no external service, and rate-limited (60 requests/minute anonymous). Returns the converted string, the echoed input, and the operation performed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to convert. For encode, the raw string to percent-encode; for decode, a percent-encoded string. Must be non-empty.
operationNoDirection of conversion. "encode" percent-encodes the text; "decode" reverses it. Decoding malformed percent sequences returns a 400 error.encode

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the conversion succeeded.
inputNoThe original text submitted, echoed back.
operationNoThe operation performed (encode or decode).
resultNoThe percent-encoded or decoded output string.
Behavior5/5

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

Description adds beyond annotations: 'pure local string transformation, read-only, non-destructive, contacts no external service, rate-limited (60 requests/minute)'. This complements readOnlyHint and idempotentHint. No contradictions.

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?

Three sentences: purpose, encoding details, usage/behavioral info. No redundancy, well-structured, and front-loaded with main action.

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?

Given simple schema (2 params, 1 required), output schema present, description covers all essential aspects: operation, use cases, alternatives, rate limiting, error states, and return fields.

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

Parameters5/5

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

Schema has 100% coverage with descriptions and examples. Description adds operational details (encoding scheme, error handling) and clarifies the operation parameter's direction, providing value beyond 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?

Description clearly states the tool percent-encodes/decodes text using encodeURIComponent semantics, lists use cases (query parameters, path segments, form data), and distinguishes from siblings like encoding_decoding_html_entities and encoding_punycode.

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?

Explicitly states when to use (for URL encoding/decoding) and when to use alternatives (HTML entities for HTML markup, punycode for international domains). Also mentions rate limit and error handling for malformed sequences.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server