ScorpTech x402 API

Home Grows

home_grows

Read-onlyIdempotent

Whether the home prime of n has more digits than n. 4, 6, and 10 do. 2 and 21 do not. A chain past 20 steps or 12 digits is rejected. n runs from 2 to 10000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/home-grows

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

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 declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond annotations: rejection at 20 steps or 12 digits, a payment cost, x402/Solana payment protocol, and an HTTPS endpoint. It does not explicitly specify the return shape or whether rejection is an error versus false.

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 predicate is front-loaded and the description uses examples, constraints, pricing, and endpoint information efficiently. It is appropriately compact for a paid single-purpose math tool, though some detail is dense.

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 one-parameter predicate with no output schema, the description covers the domain range, rejection limits, cost, and alternate HTTP invocation. It leaves the term 'home prime' and the exact boolean return/error distinction implicit, so it is useful but not fully self-contained.

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?

Schema coverage is 0%, so the description must compensate for the single parameter n. It restates the range 2 to 10000 and gives examples that imply n's role in the predicate, but it does not define 'home prime' or otherwise add much parameter meaning beyond the schema's integer 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 precise predicate: whether the home prime of n has more digits than n, backed by positive and negative examples. It is clear what the tool returns conceptually, but it does not explicitly differentiate itself from related siblings such as home_prime_len or home_prime_steps.

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 provides valid input range and rejection thresholds, which are usage constraints, but it does not say when to use this tool instead of related alternatives. An agent must infer that this is the boolean comparison helper rather than the length or step-count tool.

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?