ScorpTech x402 Tools

Landau

landau

Read-onlyIdempotent

Landau's function g(n), the largest least common multiple of the parts of a partition of n. g(0) is 1, g(5) is 6, g(7) is 12, and g(10) is 30. 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

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already establish this as a safe, read-only, idempotent operation. The description adds important behavioral context: pricing at $0.001 USDC per successful call via x402 on Solana, plus 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 front-loaded and the examples, domain, pricing, and endpoint follow efficiently. Every sentence adds practical value, though the repeated range information from the schema is slightly redundant.

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 mathematical function with no output schema, the description provides enough context to invoke it correctly: definition, domain, example outputs, cost, and transport. It could more explicitly state the return type, but the examples make the output behavior clear.

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?

With one required integer parameter and 0% schema description coverage, the description compensates by defining n as the input to Landau's function, stating the 0–25 domain, and giving example values. The range is redundant with the schema's minimum and maximum, but the mathematical meaning is clear.

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 defines Landau's function and what g(n) computes, with concrete example values. It does not explicitly differentiate this tool from sibling math tools such as landau_index or landau_sum, so it falls short of a 5.

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?

It states the valid input range but gives no guidance on when to use this tool versus related siblings. There are no exclusions, alternatives, or use-case cues.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScorpTech x402 Tools 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?