ScorpTech x402 API

Float Order

float_order

Read-onlyIdempotent

IEEE 754 totalOrder on two binary32 or binary64 values. Negative zero is below positive zero. Negative NaNs are below minus infinity and positive NaNs are above plus infinity. A larger NaN payload is farther from zero. sameBits is true only when every bit matches. form bits reads both sides as hex; the default reads them as numbers rounded ties-to-even. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/float-order

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": {
      "left": "<left>",
      "right": "<right>"
    },
    "name": "float_order"
  }
}

Input Schema

Name	Required	Default
`form`	No	value
`left`	Yes
`right`	Yes
`width`	No

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?

Adds real context beyond the read-only/idempotent annotations: an x402 pay-per-call price ($0.001 USDC, Solana) and an alternative HTTPS endpoint. This is exactly the kind of operational detail annotations cannot carry, though error/return behavior is not described.

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 core semantics and keeps every sentence informative; the pricing/endpoint note is tacked on but relevant. Slightly dense, but no wasted filler.

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 no output schema, the description should clarify the return shape; it implies a sameBits output field and an ordering result but never states the actual return structure. For a 4-param comparison tool with zero schema coverage, more return detail was needed.

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 coverage is 0%, so the description must compensate; it documents form (bits as hex vs numeric ties-to-even rounding) and implies width via binary32/binary64. However, it never specifies the format or parsing of left/right (strings up to 4000 chars), leaving the two required parameters underspecified.

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+resource ('IEEE 754 totalOrder on two binary32 or binary64 values') that clearly distinguishes it from numeric siblings like float_bits, float_ulp, or float_round. The agent can identify the operation without opening the schema.

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?

Explains the ordering semantics (negative zero, NaN placement) but never says when to use this vs float_bits/float_ulp or when a programmatic totalOrder comparison is appropriate. The form=bits note gives a hint on input handling, but there is no explicit 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?