ScorpTech x402 API

Negabinary Digit

negabinary_digit

Read-onlyIdempotent

The base -2 digit of n in place, counting from 0 at the right. For 6, which is "11010", place 0 is 0, place 1 is 1, and place 4 is 1. A place past the end is 0. n runs from 0 to 999999999999 and place runs from 0 to 60. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/negabinary-digit

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": {
      "n": "<n>",
      "place": "<place>"
    },
    "name": "negabinary_digit"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes
`place`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.9/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 behavior. The description adds meaningful operational context: place-index behavior past the end, input bounds, x402 pricing, and an HTTPS endpoint.

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?

The definition is front-loaded and compact: core semantics, example, bounds, and payment/endpoint context. It could be tightened slightly, but every sentence carries relevant information.

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 simple two-parameter math function with no output schema, the description supplies enough semantics to call it correctly: digit meaning, indexing convention, example, bounds, and past-end behavior. It does not explicitly describe invalid-n handling, but the main callable behavior is covered.

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 explain both parameters. It defines place indexing from the right, gives a concrete example, explains out-of-range place behavior, and repeats the allowed ranges for n and place.

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 states a precise computational resource: the base -2 digit of n at a given place, with an example. It clearly distinguishes this singular-digit operation from full negabinary representation or length/decoding siblings by defining the place-indexed digit.

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?

It gives mathematical constraints and an example but does not say when to use this tool versus negabinary, negabinary_bits, negabinary_decode, or negabinary_len. The usage is inferable, but no explicit routing guidance is provided.

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?