ScorpTech x402 API

Hofstadter Conway

hofstadter_conway

Read-onlyIdempotent

Conway's Hofstadter sequence. a(1) and a(2) are 1, a(6) is 4, a(10) is 6, and a(16) is 8. The rule is a(n) = a(a(n-1)) + a(n-a(n-1)). n runs from 1 to 5000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/hofstadter-conway

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds important operational context beyond annotations: the price ($0.001 USDC per successful call), the x402/Solana payment context, and an equivalent HTTPS endpoint.

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 compact and front-loads the sequence identity, examples, recurrence, and valid range. The pricing and HTTPS endpoint details are relevant for a paid x402 tool and do not feel excessive.

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?

For a simple one-parameter mathematical sequence tool with annotations and no output schema, the description provides enough context to invoke it correctly. It could be slightly more explicit about the return value being the nth term, but the recurrence and examples make this inferable.

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?

There is one parameter, n, with 0% schema description coverage. The description compensates by saying n runs from 1 to 5000 and by framing it within a(n) and the recurrence, but it still does not explicitly define n as the sequence index in plain terms beyond context.

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 Conway's Hofstadter sequence, gives its defining recurrence, and specifies the valid index range. It is specific enough for an agent to understand that the tool computes a term of this sequence, though it does not explicitly distinguish it from close siblings such as hof_conway or hof_conway_sum.

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 does not explain when to use this tool instead of related sequence tools, nor does it mention exclusions or alternatives. Usage is only implied by the sequence definition and n range.

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?