Skip to main content
Glama

Align a byte offset

bpj_discrete_align_offset
Read-onlyIdempotent

Round a byte offset up to an alignment boundary and report the required padding.

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": {
      "offset": "<offset>",
      "alignment": "<alignment>"
    },
    "name": "bpj_discrete_align_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetYes
alignmentYes

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 readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds the meaningful behavioral detail that rounding is upward (ceiling) and that padding is the reported result. It does not state the already-aligned case (padding zero) or the return shape, which matters since no output schema exists.

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 sentence with zero filler; the operation and its output are front-loaded and nothing is repeated from the title or annotations.

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 two-parameter pure arithmetic tool with full annotation coverage and no output schema, the description conveys both the operation and the returned quantity ('required padding'). Only edge-case behavior (offset already on a boundary) is left unspecified, a minor gap at this complexity level.

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 parameter meaning; it does so only conceptually, naming 'byte offset' and the 'alignment boundary' without adding semantics such as unit expectations, whether alignment must be a power of two, or behavior at alignment=1. The schema's titles and min/max bounds already supply most of what an agent can infer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Round a byte offset up to an alignment boundary and report the required padding.' That is precise enough to distinguish it from the unrelated discrete-math and encoding siblings, though it does not explicitly contrast with any named alternative.

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 operation itself (call it when you need to know alignment padding). There is no statement of when to prefer this over related offset tools, no prerequisite conditions, and no exclusions. Adequate but leaves routing 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.