ScorpTech x402 API

Byte Sum

byte_sum

Read-onlyIdempotent

The two historic Unix sums, matching GNU sum. bsd rotates the 16-bit sum right and counts 1024-byte blocks. sysv reduces modulo 65535, keeps 65535 when the total is a positive multiple of it, and counts 512-byte blocks. "123456789" is bsd 53615 and sysv 477. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/byte-sum

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": "byte_sum"
  }
}

Input Schema

Name	Required	Default
`hex`	No
`text`	No
`algorithm`	No	bsd

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4/5.0

Behavior5/5

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

With annotations already covering read-only, idempotent, and non-destructive behavior, the description adds substantial context: exact algorithm mechanics (bit rotation, modulo rules, block sizes), a worked example, per-call pricing (x402/Solana), and an alternate HTTPS endpoint. This exceeds what the annotations provide.

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 description is dense but efficiently front-loads the core purpose and algorithm semantics. Pricing and the HTTPS endpoint are appended and slightly tangential but still useful for invocation decisions.

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?

For a simple checksum tool with no output schema and covered annotations, the algorithm behavior is complete, but the two input parameters (hex/text) and the expected return format are left unexplained. Enough to call the tool, but with clear gaps.

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%, so the description must compensate. It fully explains the 'algorithm' enum semantics (bsd vs sysv) but says nothing about how 'hex' and 'text' inputs are interpreted or whether they are mutually exclusive. Partial compensation warrants a middling score.

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 names the exact operation ('historic Unix sums, matching GNU sum') and identifies the two supported variants, which distinguishes it from the many checksum/hash siblings like crc16 or fletcher16. An agent can tell precisely what this tool computes 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?

The context implies use for Unix-compatible checksums, but there is no explicit guidance on when to choose byte_sum over sibling checksum tools or when each algorithm variant is appropriate. Usage is inferable from the context but not stated.

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?