Skip to main content
Glama

basenc

Read-only

Encode or decode data into base16, base32, base64, or base64url from files or stdin. Choose any base with --base and switch to decode with --decode.

Instructions

Encode or decode data in base16 (hex), base32, base64, or base64url from files or stdin. Read-only, no side effects. Returns JSON with encoded/decoded data by default; use --raw for raw bytes on stdout. Select format with --base (default base64), switch to decode mode with --decode. Use --max_output_bytes to bound output size. Use when you need flexible base selection via a single tool. Not for fixed-format needs — use 'base64' or 'base32' for dedicated encoding. See also 'base64', 'base32'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoWrite raw encoded/decoded bytes to stdout.
baseNoBase encoding.base64
pathsNoFiles to read, or '-' for stdin. Defaults to stdin.
decodeNoDecode instead of encode.
encodingNoOutput encoding (default: utf-8). Use 'auto' for BOM/autodetection.utf-8
show_encodingNoInclude encoding detection metadata in JSON result.
encoding_errorsNoHow to handle encoding errors (default: replace).replace
encoding_profileNoLocale-aware encoding fallback profile for auto-detection.
max_output_bytesNoMaximum JSON bytes to emit.
Behavior4/5

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

Annotations provide readOnlyHint=true. Description adds 'Read-only, no side effects' and discloses behavior like JSON return, raw output via --raw, and output bounding with --max_output_bytes. 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?

The description is concise at ~60 words, front-loaded with the core action, and every sentence adds value. No redundant or missing information.

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?

Given 9 parameters with 100% schema coverage and no output schema, the description provides good context on output format, safety, and major options. Minor missing details on encoding parameter but overall sufficient.

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 3. Description explains key parameters (--raw, --base, --decode, --max_output_bytes) beyond schema, adding value. Does not detail all 9 parameters, but covers the most important ones.

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 'Encode or decode data in base16, base32, base64, or base64url', providing a clear verb and resource. It distinguishes from sibling tools by noting 'Not for fixed-format needs — use 'base64' or 'base32' for dedicated encoding.' This fully clarifies purpose.

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?

Explicit usage context: 'Use when you need flexible base selection via a single tool. Not for fixed-format needs — use 'base64' or 'base32' for dedicated encoding.' Clear when-to-use and when-not, with named alternatives.

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/caseSHY/AI-CLI'

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