ScorpTech x402 API

Fine

fine

Read-onlyIdempotent

The nth Fine number. F(0) is 1, F(1) is 0, F(2) is 1, and F(6) is 57. For n at least 1, F(n) = C(n) - sum of C(i)*F(n-1-i) over i from 0 to n-1, with C the Catalan numbers. n runs from 0 to 80. Past 15 digits the value 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/fine

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>"
    },
    "name": "fine"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile. The description adds useful behavioral context beyond annotations: the input domain, output formatting as a decimal string past 15 digits, and the $0.001 USDC x402 payment requirement.

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 every sentence is relevant to computing or paying for the tool. The recurrence and payment/endpoint details make it slightly dense, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter math tool with no output schema, the description supplies the definition, examples, valid range, recurrence, output representation past 15 digits, and payment/endpoint details. An agent has enough information to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 the parameter meaning. It fully explains n through examples such as F(0)=1, F(6)=57, the valid range 0 to 80, and the recurrence for n at least 1.

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 clearly identifies the resource as the nth Fine number, gives concrete initial values, and defines the range and recurrence. It is easy to distinguish from the broader sequence toolset, though it does not explicitly name a sibling alternative such as fine_sum.

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?

Usage is implied by the precise definition and the n range of 0 to 80, but there is no explicit guidance on when to use this tool versus siblings like fine_sum. The pricing and HTTPS endpoint add operational context rather than selection 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?