ScorpTech x402 API

Ternary Value

ternary_value

Read-onlyIdempotent

The integer written by balanced ternary digits, where T means -1. "0" is 0, "T" is -1, "1T" is 2, "10" is 3, and "1TT" is 5. A bad digit or a leading zero is rejected. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/ternary-value

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": {
      "digits": "<digits>"
    },
    "name": "ternary_value"
  }
}

Input Schema

Name	Required	Description	Default
`digits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds real value on top: it discloses rejection conditions and the pricing model ($0.001 USDC per successful call via x402 on Solana), with 'per successful call' implying failed calls are not charged. It does not describe the error response shape for rejected input.

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?

Purpose is front-loaded, and the examples, rejection rule, pricing, and HTTPS endpoint each earn their place. The opening clause 'The integer written by balanced ternary digits' is slightly awkward phrasing but not wasteful.

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 converter with no output schema, the description covers format, validity, cost, and transport alternative — enough to call it correctly. Remaining gap is the error representation for rejected input, which matters given that rejection is an expected outcome.

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 coverage is 0% and the single 'digits' parameter has no property description, so the description carries the full burden and does so: it defines the alphabet (T = -1, 0, 1), gives five concrete encodings, and states that malformed digits and leading zeros are rejected. Only the schema's maxLength of 30 is left unexplained.

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 transformation (balanced-ternary digit string -> integer) and the worked examples ("T"=-1, "1T"=2, "10"=3) make the direction of conversion unambiguous versus siblings like balanced_ternary or base_convert. It stops short of naming an alternative tool explicitly, so an agent must infer the inverse relationship.

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 context is only implied through the examples; there is no statement of when to prefer this over balanced_ternary, ternary_digit, or base_convert. The validation rule (bad digit or leading zero rejected) gives the agent a precondition, which is some guidance but not routing guidance.

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?