ScorpTech x402 API

Look Say Step

look_say_step

Read-onlyIdempotent

One look-and-say step on a digit string. 1 becomes 11, and 1211 becomes 111221. Two 2s become 22. An empty string, or a character that is not a digit, is rejected. The string stops at 4096 characters. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/look-say-step

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

Input Schema

Name	Required	Description	Default
`digits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds useful behavioral context beyond annotations: invalid input is rejected, the string is capped at 4096 characters, and the call has a specific USDC cost with an HTTPS alternative endpoint.

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 description is front-loaded with the operation and examples, then adds validation, length limit, pricing, and endpoint details. It is efficient overall, though the pricing and HTTPS endpoint sentences are useful context rather than strictly required invocation details.

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 simple one-parameter transformation tool with rich annotations and no output schema, the description is largely complete: it explains behavior, constraints, examples, and access details. The main missing piece is guidance for choosing this tool over its many look_say-related siblings.

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 parameter meaning. It does so by specifying that the input is a digit string, giving transformation examples, rejecting empty or non-digit input, and noting the 4096-character limit, though it does not explicitly name the 'digits' parameter.

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 operation: one look-and-say step on a digit string, with clear examples such as 1 becoming 11 and 1211 becoming 111221. It distinguishes this as a single-step transformation rather than a full sequence, but it does not explicitly differentiate itself from related siblings like look_say, look_say_count, look_say_len, or look_say_digit.

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 phrase 'One look-and-say step' implies the tool's usage context, but the description does not explicitly say when to choose this over look_say or the other look_say siblings. There are no stated exclusions or alternative-tool guidance, so usage is only implied.

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?