ScorpTech x402 API

Palindrome Reach

palindrome_reach

Read-onlyIdempotent

The palindrome reached by reverse-and-add. 10 reaches 11, 19 reaches 121, and 89 reaches 8813200023188. A palindrome reaches itself. If 50 steps are not enough, the input is rejected. n runs from 0 to 10000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/palindrome-reach

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

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 establish read-only, idempotent, non-destructive, open-world behavior, and the description adds meaningful context: the 50-step rejection rule, the valid input range, payment cost, and HTTPS endpoint. It does not fully specify the error response format, but the added behavioral details are substantial.

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 compact and front-loads the core definition before examples and operational constraints. It is slightly run-on, but every sentence contributes useful information about behavior, limits, or access.

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 tool with no output schema, the description provides enough information to call it correctly: examples show the return value, the 50-step limit defines failure, and cost plus endpoint details are included. Minor gaps remain around exact error semantics for rejected inputs.

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?

The single parameter has 0% schema description coverage, so the description must compensate. It does so partially by showing examples that clarify n as the starting integer and by repeating the 0–10000 range, but it does not explicitly define n or its expected format beyond those examples.

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 identifies the operation as reverse-and-add palindrome reach and gives concrete examples such as 10→11 and 19→121, making the tool’s purpose clear. It does not explicitly name sibling alternatives such as palindrome_steps or reverse_add, so it falls short of full sibling differentiation.

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 states a 50-step rejection condition and the input range, but it does not explain when to choose this tool over related siblings like palindrome_steps, reverse_add, or lychrel. The usage is implied by the mathematical operation rather than explicitly guided.

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?