Skip to main content
Glama

Estimate Base64 payload size

bpj_estimate_base64_size
Read-onlyIdempotent

Calculate padded Base64 length, wrapping overhead and whether the encoded payload fits a byte budget.

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": {
      "bytes": "<bytes>",
      "wrapperBytes": "<wrapperBytes>",
      "budgetBytes": "<budgetBytes>"
    },
    "name": "bpj_estimate_base64_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
bytesYes
budgetBytesYes
wrapperBytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world, so safety behavior is well covered. The description adds only a high-level statement of what is calculated and does not explain formula assumptions, rounding, or how wrapping overhead is determined beyond the parameter names.

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 front-loaded sentence with no filler. It states the tool's outputs efficiently, though that efficiency contributes to the parameter-semantics gap rather than being a structural flaw.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small calculator tool with no output schema, the description states the computed outputs adequately enough to understand the basic intent. However, with three required parameters and zero schema descriptions, the definition leaves important input semantics such as wrapperBytes unexplained, which is a meaningful completeness gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for three required parameters, but it only vaguely references 'byte budget' and 'wrapping overhead'. It does not clarify whether wrapperBytes is a byte count, a per-line overhead, or how it interacts with the Base64 calculation, so meaningful parameter semantics remain largely undocumented.

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 uses a specific verb, 'Calculate', and names the exact quantities produced: padded Base64 length, wrapping overhead, and byte-budget fit. This makes the tool's purpose clear and distinguishable from the surrounding calculator-style siblings without needing to inspect the schema.

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 its use case: estimating encoded payload size against a budget. However, it gives no explicit when-to-use guidance, no exclusions, and no comparison to alternative tools, leaving usage context to inference.

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.