camelotwebtools-mcp

camelot_base64_encoder

Idempotent

Convert text to Base64 or decode Base64 back to text entirely in your browser, keeping data local. Choose encode or decode mode and process input instantly.

Instructions

Base64 Encoder: Encode and decode text strings and binary data to/from Base64 format locally.. Local browser processing. Canonical URL: https://www.camelotwebtools.com/tools/base64-encoder

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Operating mode or formatting style	encode
`text`	Yes	Input text to encode, decode, format, or process

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Execution status of the tool (success or error)
`prefillUrl`	Yes	Direct deep-link URL to view, edit, and export in Camelot Web Tools
`canonicalUrl`	Yes	Canonical web URL for this tool on camelotwebtools.com
`documentTitle`	Yes	Title of the generated document, report, or calculation output
`documentMarkdown`	Yes	Complete structured output and body formatted in clean Markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 16, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already provide idempotent and non-destructive hints. The description adds the useful context that processing happens locally in the browser, but it does not clarify behavior for invalid Base64 input, size limits, or how binary data is represented in the text field.

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?

Purpose is front-loaded and the description is relatively compact. However, it includes a redundant 'locally' and 'Local browser processing' and a canonical URL that is not actionable for tool invocation.

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 two-parameter tool with an output schema and annotations, this description is nearly complete. It covers the operation, the local execution context, and the encode/decode modes; minor gaps around binary-data handling and usage alternatives remain.

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?

Schema coverage is 100%, so parameters are already well documented. The description's mention of encode/decode aligns with the mode enum replication, though it doesn't add specific parameter-level details beyond the 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?

The description explicitly states the tool 'Encode and decode text strings and binary data to/from Base64 format locally,' which names the exact operation and resource. This clearly differentiates it from sibling tools like camelot_url_encoder or camelot_hash_generator.

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?

The description implies the tool should be used when Base64 encoding or decoding is needed, but it does not explicitly name alternatives or state when not to use it. No comparison to URL encoding, hashing, or other coders is provided.

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

Deploy Server