Skip to main content
Glama

Codificar quoted-printable

quoted-printable-encode
Read-onlyIdempotent

Codifica texto como quoted-printable MIME (RFC 2045). Cuándo: hay que convertir bytes o texto a esta codificación, o desde ella, con exactitud y sin adivinar. No para: decodificar quoted-printable MIME a texto UTF-8 (quoted-printable-decode). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Encodes UTF-8 text as MIME quoted-printable (RFC 2045): =XX escapes, 76-char soft line breaks, CRLF line endings. When: bytes or text have to be converted to or from this encoding exactly, without guessing. Not for: decoding MIME quoted-printable (quoted-printable-decode). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB.

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": {
      "text": "<text>"
    },
    "name": "quoted-printable-encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText (string; required).

Output Schema

NameRequiredDescriptionDefault
encodedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / text / examples
      Added value: +[
      +  "café = 3€"
      +]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description adds crucial behavioral constraints not covered by the annotations or schema, including explicit limits (64KB input, 1MB output), side effects (none, read-only), and the deterministic nature of the operation.

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?

Despite being bilingual and lengthy, the information is highly organized into distinct, high-value blocks (Definition, When, Not For, Side Effects, Limits). Every sentence adds a unique and necessary piece of information.

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?

This definition is extremely complete. It covers technical specifications (RFC 2045, line endings), operational limits (time, size), and behavioral guarantees (deterministic, side effects), leaving no major technical gap for the agent to interpret.

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?

Since schema coverage is 100%, the baseline is high. The description clarifies that the required 'text' parameter is a string, reinforcing its necessity and type, although the schema itself handles the majority of the semantic burden.

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 precisely defines the tool's function as encoding UTF-8 text into MIME quoted-printable format (RFC 2045). It is highly specific and clearly differentiates itself from other encoding tools in the sibling list, such as base64-encode or quoted-printable-decode.

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?

It provides explicit 'When' and 'Not for' sections. Specifically, it advises the user to use this tool for conversion tasks and names the alternative sibling (quoted-printable-decode) that it should not replace.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources