Skip to main content
Glama

Solana Signal

List unlimited paid endpoints

paid_endpoints
Read-only

List all Solana Signal API x402 pay-per-call endpoints (USDC on Solana, no API key): token risk, wallet portfolio, token prices, tx explain, wallet activity, pump.fun launches and migrations, with prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "paid_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this as a safe read (readOnlyHint=true). The description adds real context beyond that: the endpoints are x402 pay-per-call, billed in USDC on Solana, require no API key, and the listing includes prices. It does not say whether calling the listing itself costs anything or what the price units look like, which keeps it from a 5.

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?

One front-loaded sentence beginning with the verb and resource, with the endpoint categories acting as informative scope. The enumeration is dense but each item earns its place by telling the agent what is purchasable; only the trailing "with prices" feels tacked on.

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 zero-parameter, no-output-schema listing tool, the description covers what is returned (endpoint names, categories, prices) and the payment model. It stops short of explaining the response shape or how an agent should proceed to actually call a paid endpoint, which is the remaining gap.

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?

The tool takes zero parameters, so the schema carries no semantic burden and the baseline is 4. However, the description supplies no invocation detail either (e.g., whether filters or paging exist), and with an empty parameter object there is simply nothing for it to clarify, so it lands at an adequate middle score rather than adding meaning.

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: "List all Solana Signal API x402 pay-per-call endpoints," then enumerates the endpoint categories (token risk, wallet portfolio, token prices, tx explain, wallet activity, pump.fun launches/migrations). This clearly marks it as an endpoint catalog rather than one of the sibling endpoint tools (token_risk, token_prices, tx_explain), so an agent can distinguish it 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?

Usage is only implied: the word "List" plus "pay-per-call" suggests discovery of purchasable endpoints, and "no API key" hints at access conditions. There is no explicit when-to-use, no statement of the relationship to the sibling endpoint tools (e.g., call this first to discover endpoints, then invoke the specific one), and no exclusions.

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