ScorpTech x402 Tools

Betrothed

betrothed

Read-onlyIdempotent

Whether n and m are betrothed: the sum of proper divisors of n is m+1, and the sum for m is n+1, with m different from n. 48 pairs with 75, and 140 pairs with 195. The partner is 0 when n is not betrothed. n runs from 1 to 100000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/betrothed

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description only needs to add operational context — and it does: paid x402 endpoint at $0.001 USDC per successful call, plus an alternative HTTPS/POST route. It also discloses the response convention (0 for non-betrothed) which the agent needs to interpret a result correctly.

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 and examples lead, followed by output convention, bound, and payment/transport metadata — a sensible front-loading order with no filler sentences. Slightly dense with formula, examples, pricing, and URL in one paragraph, but every element carries information the caller needs.

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?

With no output schema, the description must explain the return value — it does (the partner m, or 0 if none). Input domain, payment model, and transport alternative are all covered, so an agent has everything needed to call and interpret the tool.

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%, so the description must carry the meaning of `n`. It does: n is the integer to test, it must lie in 1..100000, and its role in the divisor-sum condition is spelled out. The range repeats the schema's min/max, but the semantic role of n is genuinely added.

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?

States the exact mathematical predicate (proper-divisor sums equal m+1 / n+1, m ≠ n) so the tool cannot be confused with amicable, sociable, or aliquot siblings. Two worked examples (48↔75, 140↔195) make the definition unambiguous.

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 domain (n from 1 to 100000) and the 'partner is 0 when not betrothed' convention implicitly tell the agent the input contract, but there is no explicit when-to-use vs. alternatives (e.g. amicable, sociable) or statement of when not to call it. Usage is inferable from the definition rather than stated.

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?