Skip to main content
Glama

Extract an unsigned bit field

bpj_bitfield_extract
Read-onlyIdempotent

Extract a field from a 64-bit unsigned word using a zero-based least-significant-bit offset.

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>",
      "offset": "<offset>",
      "bits": "<bits>"
    },
    "name": "bpj_bitfield_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitsYes
offsetYes
integerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered. The description adds the meaningful behavioral detail that offsets are zero-based from the LSB, but says nothing about what happens if offset + bits exceeds 64, how out-of-range input is rejected, or what form the result takes.

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?

A single sentence with the key constraint (64-bit unsigned, zero-based LSB offset) front-loaded and no filler. It is efficient, though its brevity leaves the coverage gaps noted elsewhere.

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 three-required-parameter tool with zero schema documentation and no output schema, the description should state the result format and boundary behavior. It covers the encoding convention but leaves an agent guessing what an out-of-range offset+width does and whether the return is decimal, hex, or a string.

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% and the schema supplies only titles ('Bit width', 'Bit offset', 'Decimal integer'). The description compensates partially: it establishes the 64-bit unsigned range of 'integer' and clarifies 'offset' as zero-based LSB indexing. It never explains whether 'bits' is a width starting at offset, or what units/format the result is returned in.

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 ('Extract') and resource ('a field from a 64-bit unsigned word'), plus the addressing convention. An agent can tell this is bit-level extraction rather than, say, byte encoding or LEB128 decoding. It stops short of naming a sibling alternative, so a 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. the integer must fit in 64 unsigned bits), and no pointer to any alternative tool. The only usage signal is implicit in the phrase '64-bit unsigned word'.

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.