ScorpTech x402 API

Repunit

repunit

Read-onlyIdempotent

The repunit of length n, (10^n - 1)/9. R1 is 1 and R2 is 11. n = 0 is rejected. n runs up to 500. 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/repunit

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

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 declare read-only, idempotent, non-destructive behavior, and the description adds genuinely useful facts beyond them: a per-call cost of $0.001 USDC via x402 on Solana, an equivalent HTTPS endpoint, an error case (n = 0), and a return-type switch to a decimal string past 15 digits. What it omits is any note on payment/authorization mechanics or rate limits beyond the unit price.

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?

Front-loaded with the definition and formula, then bounds, output format, and pricing — each sentence adds information. The style is telegraphic, and the pricing/endpoint sentence, while operationally relevant, is commercial boilerplate.

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 a single parameter, no output schema, and annotations covering the safety profile, the description supplies what an agent needs: the computation, valid domain, failure case, and result representation. Only the exact return shape for n <= 15 remains implicit.

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 coverage is 0% and the schema's own bounds (minimum 0, maximum 500) conflict with the description's 'n = 0 is rejected', so the description carries the burden and mostly succeeds: it defines n as the repunit length, gives examples, restates the upper bound, and warns that 0 fails. It could be sharper about the output type for small n (integer vs string) to fully close the gap.

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?

Names the exact mathematical object and gives its closed form, (10^n - 1)/9, plus worked examples (R1 = 1, R2 = 11), so there is no ambiguity about what is computed. Among the hundreds of number-theory siblings, this identifies a single well-defined sequence term.

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?

The description constrains inputs (n = 0 rejected, n up to 500) but never states when to reach for this tool versus an alternative, nor any prerequisite workflow. Usage is only implied by the math definition.

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?