ScorpTech x402 API

Landau Mod

landau_mod

Read-onlyIdempotent

g(n) mod m for Landau's function. g(12) mod 7 is 4, and g(25) mod 97 is 96. The modulus is a positive decimal integer, and zero is rejected. n runs from 0 to 25. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/landau-mod

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

Input Schema

Name	Required	Description	Default
`n`	Yes
`mod`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.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 meaningful context beyond them: pricing, x402/Solana payment, HTTPS endpoint, and zero rejection for the modulus; it does not detail error behavior beyond zero.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The formula is front-loaded, examples are compact, and constraints and payment details are stated without filler. Every sentence adds useful information for invoking the tool correctly.

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 simple two-parameter mathematical function with no output schema, the description supplies the formula, examples, input constraints, cost, and alternate endpoint. Annotations cover the safety profile, so no essential context is missing.

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 explains that mod is a positive decimal integer with zero rejected and that n ranges from 0 to 25; the 600-digit limit is left to the schema, but examples clarify the inputs and output.

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 a specific computation, g(n) mod m for Landau's function, and gives worked examples. It distinguishes this modular-result tool from siblings like landau, landau_sum, and landau_index.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The valid input domain for n and the modulus rule are clearly stated, so the context for use is unambiguous. It does not explicitly name alternatives such as landau for the full value, so it falls short of a 5.

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?