Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

math_bitwise_calculator

Read-onlyIdempotent

Perform bitwise operations (AND, OR, XOR, NOT, NAND, NOR, shifts) on integers with selectable input base and bit width, returning results in binary, octal, decimal, and hex simultaneously.

Instructions

Bitwise Calculator. Perform a bitwise operation on integers with a selectable input base and bit width. operation chooses AND, OR, XOR, NOT, NAND, NOR, or a shift (shl, shr, ushr); pass operation=parse instead to just convert one value into all four bases. Operands accept base 2/8/10/16 (optional 0x/0b/0o prefix) at width 32 or 64, signed or unsigned, and the result is returned in binary, octal, decimal, and hex at once. Use this for bit-level logic and shifts; use conversion_number_base for plain radix conversion and math_scientific_calculator for arithmetic expressions. Pure local computation: read-only, non-destructive, deterministic, contacts no external service, and is rate-limited (60 requests/min anonymous).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesBitwise op to run. and/or/xor/nand/nor need a and b; not is unary (a only); shl/shr/ushr shift a left or right by b bits (shr is arithmetic when signed, ushr is logical). Use parse to convert value into every base instead.and
aYesFirst operand (or the value to shift). String or number in base aBase; optional 0x/0b/0o prefix must match aBase. Negative only allowed when signed is true. Not used when operation=parse.
bNoSecond operand for and/or/xor/nand/nor, or the shift count (0 to width-1) for shl/shr/ushr, in base bBase. Omit for not and parse.
aBaseNoRadix used to read operand a. 2=binary, 8=octal, 10=decimal, 16=hex.
bBaseNoRadix used to read operand b / the shift count.
widthNoInteger bit width. Operands are masked to this width; shift counts must be less than it.
signedNoInterpret values as two's-complement signed (allows negative input and arithmetic shr) when true; unsigned when false.
valueNooperation=parse only: the value to convert into all four bases, read using fromBase.
fromBaseNooperation=parse only: radix of value. Required when operation=parse.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the operation succeeded.
operationNoEchoes the requested operation (and/or/.../parse).
resultNoBitwise op returns a/b/operation/width/signed plus a nested result with binary/octal/decimal/hex. operation=parse returns value/fromBase/width/signed/decimal/binary/octal/hex.
Behavior5/5

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

Description adds behavioral context beyond annotations: 'read-only, non-destructive, deterministic, contacts no external service, rate-limited (60 requests/min anonymous).' No contradiction with annotations.

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?

Front-loaded with purpose, lists operations, explains operand/result behavior, then provides usage guidance. Efficient single paragraph with no wasted words.

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?

Covers all key aspects: operations, operands, bases, width, signedness, result format, and parse mode. Output schema exists, so return format is covered. Complete for the complexity.

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?

While schema coverage is 100% (baseline 3), the description adds value by explaining shift semantics (e.g., shr vs ushr with signed) and the parse operation, enhancing understanding beyond the schema.

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 clearly states it performs bitwise operations on integers with selectable base and width, and distinguishes itself from sibling tools like conversion_number_base and math_scientific_calculator by specifying use cases.

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?

Explicitly states when to use this tool vs. alternatives, e.g., 'Use this for bit-level logic and shifts; use conversion_number_base for plain radix conversion and math_scientific_calculator for arithmetic expressions.' Also mentions rate limits and local computation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server