ScorpTech x402 API

Lucky Twin

lucky_twin

Read-onlyIdempotent

Whether n and n+2 are both lucky. 1, 7, and 13 start a lucky pair. 3 does not, because 5 is not lucky. n runs from 1 to 99985. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/lucky-twin

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

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?

The annotations already cover safety traits such as read-only, idempotent, and non-destructive behavior. The description adds important behavioral context beyond the annotations by disclosing the input range, the paid x402/Solana cost model, and the 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 purpose is front-loaded and the examples clarify the predicate efficiently. The payment and HTTPS details are relevant, though the definition is slightly longer than a minimal invocation-focused description would need.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter predicate, the description covers the input domain, examples, cost, and endpoint. However, with no output schema, it does not explicitly state that the return value is a boolean or otherwise describe the response shape.

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 has to carry parameter meaning, and it does explain that n is the number being tested for a lucky-twin relationship. It also gives examples and restates the valid range of 1 to 99985, though the schema already encodes the numeric bounds.

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 states a specific predicate over the input: whether n and n+2 are both lucky. It gives examples that make the condition concrete, but it does not explicitly contrast the tool with nearby siblings such as lucky, lucky_next, or lucky_nth.

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 defines the predicate but gives no explicit guidance about when to choose this over sibling lucky-number tools. There are no named alternatives, exclusions, or routing conditions.

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?