Skip to main content
Glama

ScorpTech x402 Tools

Achilles

achilles
Read-onlyIdempotent

Whether n is an Achilles number: powerful, but not a perfect power. 72 and 108 are Achilles. 36 is a square, and 1 is a perfect power, so neither is Achilles. n runs from 1 to 1000000000000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/achilles

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

Input Schema

NameRequiredDescriptionDefault
nYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds meaningful behavioral context beyond annotations: per-call pricing, the x402/Solana payment mechanism, and 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded, followed by concise clarifying examples, the input range, and practical access/pricing information. Every sentence contributes useful information with no padding.

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?

For a single-parameter boolean mathematical predicate with no output schema, the description supplies the definition, examples, valid range, and access details. Nothing material is missing for correct invocation.

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 must carry the burden for the single parameter n. It does so by stating the valid domain (1 to 1000000000000) and giving concrete example values that clarify what counts as an Achilles number.

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 gives a specific predicate with a precise mathematical definition: "Whether n is an Achilles number: powerful, but not a perfect power." It also supplies examples (72 and 108 yes; 36 and 1 no), which makes the tool's purpose unambiguous and distinguishable from generic number-property siblings.

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?

Usage is implied by the clear predicate form, and the domain constraint is stated (n from 1 to 1000000000000). However, the description does not explicitly say when to prefer this tool over related siblings such as powerful or perfect_power, nor does it state exclusions or alternatives.

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