ScorpTech x402 API

Float Bits

float_bits

Read-onlyIdempotent

Explain an IEEE 754 binary32 or binary64 value. Pass bits as hex, or a decimal or fraction, which is rounded ties-to-even. Returns the class, sign, unbiased exponent, fraction bits, and the exact value. Negative zero stays negative. The word nan is the quiet NaN; snan is the signaling NaN with payload 1. The top fraction bit is the quiet bit. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/float-bits

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "float_bits"
  }
}

Input Schema

Name	Required	Description	Default
`bits`	No
`value`	No
`width`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the returned fields (class, sign, unbiased exponent, fraction bits, exact value), special-case semantics (negative zero stays negative, nan vs snan with payload, quiet bit), ties-to-even rounding, and the x402 pricing plus HTTPS fallback.

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?

Front-loads the purpose, then input formats, then return semantics, then pricing/endpoint. Dense but every sentence carries information; the pricing/endpoint sentence is necessary for the payment model rather than filler.

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?

With no output schema, the description steps in to name the return fields and special-value handling, and it discloses the cost model. The main residual gap is failing to clarify the 'width' parameter's role and default, which matters for interpreting binary32 vs binary64 output.

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 carries the burden. It explains the 'bits' format (hex) and 'value' format (decimal or fraction, ties-to-even rounded) and implies the width choice via binary32 vs binary64, but never names the 'width' parameter or its default of 64, leaving one of three params implicit.

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?

States a specific verb and resource: 'Explain an IEEE 754 binary32 or binary64 value.' This distinguishes it from the other float siblings (float_next, float_round, float_ulp, float_order), which perform transformations rather than bit-level inspection.

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

Usage Guidelines4/5

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

Gives clear input-mode guidance (pass bits as hex, or a decimal/fraction which is rounded ties-to-even), which tells the agent how to invoke it. It does not explicitly exclude or route to siblings such as float_ulp or float_round, so it stops short of full when/when-not guidance.

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?