Skip to main content
Glama

toolkit-mcp-server: encode value

toolkit_encode_value
Read-onlyIdempotent

Encode or decode text using base64, base64url, hex, or URL percent-encoding. Supports both encoding raw UTF-8 text and decoding back to original text with error reporting for malformed input.

Instructions

Encode or decode a value across base64, base64url, hex, or URL (percent) encoding, in either direction. Set operation to "encode" to transform raw UTF-8 text into the chosen encoding, or "decode" to recover the original text from an encoded value. base64url uses the URL-safe alphabet (- and _ instead of + and /); url applies encodeURIComponent / decodeURIComponent. Decoding a value that is malformed for the chosen encoding is reported as a recoverable error, not a silent best-effort.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesThe value to transform — raw text for encode, an encoded string for decode.
encodingYesThe encoding to apply: base64, URL-safe base64url, hex, or URL percent-encoding.
operationYes"encode" transforms text into the encoding; "decode" recovers text from an encoded value.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe transformed value (encoded text, or the decoded original).
encodingYesThe encoding that was applied.
operationYesThe operation that was performed.
Behavior4/5

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

Annotations already indicate readOnlyHint and idempotentHint, so the tool is safe and idempotent. The description adds valuable behavioral context, such as error handling for malformed decode values, which goes beyond annotations.

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?

The description is a single paragraph that is well-structured and concise. Every sentence adds important information without redundancy, making it easy for an AI agent to quickly grasp the tool's functionality.

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 the tool's moderate complexity (4 encodings, 2 operations) and the presence of an output schema (not shown but referenced), the description covers all essential aspects: supported encodings, operation directions, and error behavior. No significant gaps remain.

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 baseline is 3. The description adds context by explaining that 'value' is raw text for encode and encoded string for decode, and clarifies the 'encoding' options with examples. This provides incremental value over the schema descriptions.

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 the tool's purpose: encoding/decoding across base64, base64url, hex, and URL encodings. It specifies the operation (encode/decode) and distinguishes itself from sibling tools like toolkit_hash_value, which handles hashing.

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 provides clear guidance on when to use encode vs decode, and mentions that malformed decode values result in a recoverable error. However, it does not explicitly state when not to use this tool or list alternatives beyond the implicit sibling distinctions.

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/cyanheads/toolkit-mcp-server'

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