Skip to main content
Glama

Encode unsigned LEB128

bpj_unsigned_leb128
Read-onlyIdempotent

Encode an unsigned 64-bit integer as little-endian base-128 bytes.

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": {
      "integer": "<integer>"
    },
    "name": "bpj_unsigned_leb128"
  }
}

Input Schema

NameRequiredDescriptionDefault
integerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered and the description adds nothing there. The description does not disclose how the resulting bytes are surfaced (hex string, byte array, or other), which is the main behavioral detail an agent would want for a no-output-schema tool.

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?

A single front-loaded sentence with no filler, no repetition of the title, and no redundant restatement of annotations. Nothing could be trimmed without losing information.

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 one-parameter pure function with full safety annotations, the definition covers input type and encoding semantics but leaves the return representation unspecified, and there is no output schema to fill that gap. An agent knows what to send but not exactly what shape of bytes to expect back.

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 description coverage is 0%, so the description must carry the load; it partially does by specifying 'unsigned 64-bit', which tells the agent the valid range is 0 to 2^64-1 and that negatives are out of scope. However it never states that the argument is passed as a decimal string (only the schema's title hints at that) and says nothing about the maxLength-25 bound.

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?

Names a specific verb (Encode), a specific input type (unsigned 64-bit integer) and a specific output encoding (little-endian base-128 bytes), which is precisely what LEB128 means. An agent can tell exactly what this does without opening anything else; none of the listed siblings overlap.

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?

Usage is only implied by the tool's nature as a self-contained pure encoder; there is no explicit statement of when to use it, no mention of a corresponding decode tool, and no note about when a different numeric encoding would be preferred. For a single-purpose primitive this is adequate but not instructive.

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.