Skip to main content
Glama

Build a two’s complement word

bpj_twos_complement_word
Read-onlyIdempotent

Validate the signed range and display the target-width binary word and unsigned value.

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

Input Schema

NameRequiredDescriptionDefault
bitsYes
integerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real value on top: it discloses that a signed-range validation occurs (implying a failure mode for out-of-range input) and that the result contains both a binary word and an unsigned value, which matters because there is no output schema.

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 no filler, ordered as validation then output. It is efficient, though the terseness borders on under-specification rather than true conciseness.

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?

With two required parameters, no output schema, and zero schema coverage, the agent needs input-format and edge-case information that the description does not supply (string-encoded integer, out-of-range behavior). The output disclosure and validation hint keep it at a viable level, but gaps remain.

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% for both required parameters, so the description carries the burden. 'Target-width binary word' implies the `bits` width, and 'signed range' implies `integer`, but nothing explains that the integer is supplied as a decimal string (max 25 chars) or how negative values are treated, leaving the two parameters only partially illuminated.

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 concrete operations (validate a signed range, emit a target-width binary word and unsigned value), which together identify a two's-complement conversion. A reader can tell what the tool produces, though the phrase 'two's complement' itself only appears in the tool title, and no sibling is referenced for contrast.

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 guidance, no mention of prerequisites (e.g., the integer must fit the given bit width), and no routing toward or away from any alternative tool. The agent must infer applicability entirely from the operation described.

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.