ScorpTech x402 Tools

Fuss Check

fuss_check

Read-onlyIdempotent

The Fuss-Catalan division. num is C(pn+1, n), den is pn+1, and value is the exact quotient. p runs from 1 to 8 and n from 0 to 30. Past 15 digits a part is a decimal string. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/fuss-check

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": {
      "p": "<p>",
      "n": "<n>"
    },
    "name": "fuss_check"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes
`p`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds meaningful context beyond annotations: pricing per successful call, x402/Solana payment mechanics, an HTTPS endpoint, and output formatting as decimal strings past 15 digits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the operation and formula, then adds ranges, output formatting, and access/payment details. Every sentence contributes useful invocation information without wasteful prose.

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 explains the output parts num, den, and value and notes the decimal-string format for large values. It covers the key computational and access details, though error or payment-failure behavior is not described.

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 carry parameter meaning. It defines p and n through the formula and repeats their numeric ranges, which compensates partially, but it does not explain the semantic role of p beyond its use in the quotient.

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?

The description states a specific mathematical operation, 'Fuss-Catalan division,' and gives the exact formula for num, den, and value. It is clear enough to distinguish this computation from generic Catalan tools, though it does not explicitly name or contrast the sibling fuss_catalan tool.

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?

The description gives parameter ranges and pricing but no explicit guidance on when to use this tool versus alternatives such as fuss_catalan or catalan. Usage is only implied by the mathematical formula.

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

All ScorpTech x402 Tools 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?