Skip to main content
Glama

ScorpTech x402 Tools

Kaprekar

kaprekar
Read-onlyIdempotent

Whether n is a Kaprekar number. Split n^2 so the right part has as many digits as n; the two parts add to n, and the right part is not 0. 1, 9, 45, 297, and 9999 are. 10 is not. n runs from 1 to 10000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/kaprekar

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

Input Schema

NameRequiredDescriptionDefault
nYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description provides essential operational data (pricing, API endpoint, host) and input constraints. These details go significantly beyond the read-only and destructive hints provided in the annotations, offering a complete behavioral profile.

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 starts with the core purpose, followed by the formal definition, examples, constraints, and then operational details. It is highly dense but organized for comprehensive coverage.

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?

The tool is a specialized checker. Given the explicit definition of the mathematical concept, the required input domain, and the associated operational costs/endpoints, the definition is fully complete for an AI agent to utilize it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 define the parameter. It explains exactly what the parameter 'n' represents (the number being tested) and provides concrete examples (1, 9, 45, 10), making the parameter perfectly clear.

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 defines the specific mathematical concept (Kaprekar number) and states the tool's function clearly. Given the large set of sibling number theory tools, the detailed definition helps an agent select this tool over similar complex functions.

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?

It explicitly states the bounds of the input parameter 'n' (runs from 1 to 10000), which is critical usage context. While it doesn't guide the agent toward alternatives for different mathematical domains, it sets strict operational scope.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources