ScorpTech x402 API

Negabinary Decode

negabinary_decode

Read-onlyIdempotent

The integer written by a base -2 bit string. "0" is 0, "110" is 2, "100" is 4, and "11010" is 6. A character other than 0 or 1, or a leading zero, is rejected. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/negabinary-decode

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

Input Schema

Name	Required	Description	Default
`bits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond them: invalid characters and leading zeros are rejected, and each successful call costs $0.001 USDC via x402 on Solana, which matters for an agent's decision to call. Return type is only implied ("the integer").

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?

Purpose and examples come first, then validation rules, then pricing and the HTTPS endpoint. Every sentence earns its place, though the HTTP-endpoint sentence is somewhat tangential for an MCP caller.

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 one-parameter pure function with no output schema, the description supplies the semantics (base -2), the input contract, and the failure conditions, which is enough to call correctly. The only real omission against a large sibling set is a pointer to the encode counterpart.

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?

Schema coverage is 0%, so the description must carry the single parameter, and it largely does: the value must be a string of 0s and 1s, no other characters, no leading zero. Length bounds (1-40) live only in the schema, which is a minor residual gap.

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?

States the resource and operation concretely: converts a base -2 bit string into the integer it encodes, reinforced by three worked examples ("110" is 2, "100" is 4, "11010" is 6). What it does not do is distinguish itself from the sibling family (negabinary, negabinary_bits, negabinary_len), so an agent could confuse decode with the encoder.

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: the examples make clear this takes a bit string, and the rejection rules hint at the input contract. There is no explicit statement of when to pick this over negabinary (the likely inverse) or negabinary_bits/negabinary_len, and no prerequisites beyond the price note.

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

All ScorpTech x402 API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?