ScorpTech x402 API

Morse Encode

morse_encode

Read-onlyIdempotent

Encode text as international Morse (ITU-R M.1677). Letters are separated by one space and words by " / ". SOS is ... --- ... Digits and the recommendation punctuation are included. Other characters are rejected. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/morse-encode

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": {
      "text": "<text>"
    },
    "name": "morse_encode"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, it discloses important behavior: exact Morse formatting rules, character rejection, price per successful call, x402/Solana payment context, and an alternate HTTPS endpoint. The annotations already declare read-only/idempotent/non-destructive behavior, and the description adds useful operational context.

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 core purpose is front-loaded in the first sentence, followed by relevant formatting, character support, pricing, and endpoint details. The description is compact and every sentence supports correct invocation or understanding of the tool.

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 encoding tool with no output schema, the description provides enough detail to call it correctly: supported character scope, separators, rejection behavior, and output format implied by examples. Payment and endpoint information are also included.

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?

The schema only documents a required string with maxLength 500 and no description coverage. The description compensates by explaining that the input is text to encode, that digits and recommended punctuation are accepted, that other characters are rejected, and how letters and words are separated.

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 states a specific verb and resource: encode text as international Morse (ITU-R M.1677). The sibling set includes morse_decode, morse_run, and morse_timing, and the encode/decode distinction is clear from the verb alone.

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 gives clear usage context by specifying supported character classes, separators, and rejection of other characters. It does not explicitly route the agent to alternatives such as morse_decode or morse_timing, but the encode use case is unambiguous.

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?