ScorpTech x402 API

Sol Signatures

sol_signatures

Read-onlyIdempotent

Recent transaction signatures that touched a Solana address (wallet, token account, mint or program), newest first, via getSignaturesForAddress: signature, slot, block time and age, success or error, memo and confirmation status, plus a summary (failed count, time span, rough tx/hour). Paginate with before=. Public Solana RPC, read-only. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/sol-signatures

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": {
      "address": "<address>"
    },
    "name": "sol_signatures"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Signatures to return (1-100)
`before`	No	Start searching backwards from this signature (pagination)
`address`	Yes	Solana address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds material context the annotations cannot: it runs on public Solana RPC, results are newest-first, and it costs $0.005 USDC per successful call via x402 with a matching HTTPS endpoint. Rate limits and error-surface behavior are the only gaps.

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 purpose and scope are front-loaded in the first clause, and the pricing/endpoint details sit at the end where they belong. It is a long single paragraph, but nearly every clause carries distinct information (returned fields, pagination, cost, transport).

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?

There is no output schema, yet the description enumerates the returned fields (signature, slot, block time/age, status, memo, confirmation, summary stats), so return values need no further explanation. Combined with pricing and endpoint disclosure, the definition is essentially call-ready; only pagination limits and failure behavior are unaddressed.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so limit, before, and address are already documented; that sets the baseline of 3. The description adds only that before= drives backward pagination, which mildly reinforces but does not exceed the schema's own wording.

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?

States a specific verb and resource (recent transaction signatures for an address), enumerates the address types it accepts (wallet, token account, mint, program), names the underlying RPC method, and fixes the ordering (newest first). An agent can tell this is a signature-list tool rather than the transaction-detail siblings (solana_tx, sol_tx_status) without opening the schema.

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?

It gives concrete pagination guidance ('Paginate with before='), which is real usage help, but it never states when to reach for this versus solana_tx or sol_tx_status, nor any prerequisite beyond a valid base58 address. The when-to-use context is implied rather than articulated.

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?