ScorpTech x402 API

Schroder Little

schroder_little

Read-onlyIdempotent

The nth little Schröder number. It is 1 at n = 0 and half the large Schröder number for n > 0. s(5) is 197. n runs from 0 to 64. 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/schroder-little

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful operational details beyond annotations: the valid n range 0-64, the return format switching to a decimal string past 15 digits, the exact x402 price per successful call, and an alternate HTTPS endpoint. Error behavior for invalid inputs is not described, keeping it from a 5.

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 front-loaded with the mathematical definition and then layers in range, output-format, pricing, and endpoint information. Every sentence contributes useful context, though the pricing and HTTPS endpoint details add some length beyond pure mathematical semantics.

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?

There is no output schema, so the description must explain return values, which it does by giving an example (197) and specifying that results past 15 digits are returned as a decimal string. Combined with the valid input range and cost model, this is complete enough for an agent to invoke the tool correctly.

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 description coverage is 0%, so the description must carry parameter meaning. It defines n as the index of the sequence, states the valid range 0-64, and gives two concrete values (s(0)=1 and s(5)=197), which compensates well for the missing schema descriptions. It does not explain what happens for out-of-range n.

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 states exactly what the tool computes: 'The nth little Schröder number.' It adds a defining relation to the large Schröder number, a concrete example (s(5)=197), and the valid input range, so an agent can distinguish it from the sibling 'schroder' tool 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?

Usage is implied by the mathematical definition and the mention that it is half the large Schröder number for n > 0, but the description never explicitly says when to choose this tool over the sibling 'schroder' or other sequence tools. No prerequisites or exclusions are given.

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?