Skip to main content
Glama

My MCP Server

sol-usdc-spread-scanner

Live Solana Mainnet sol-usdc-spread-scanner ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

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": "sol-usdc-spread-scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one genuinely useful behavior — cost of $0.10 USDC and the x402 v2 PAYMENT-SIGNATURE header requirement — but says nothing about read-only vs mutating behavior, rate limits, latency, or what the scan returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with no filler, which is good, but it is a parenthetical fragment rather than a structured description. Conciseness here is achieved through omission rather than economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and two undocumented optional parameters, the description would need to explain behavior and return shape. It only covers payment mechanics, leaving an agent unable to predict what a call produces or how to populate mint and targetWallet.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters (mint, targetWallet), and the description adds no meaning for either — not their format, whether they are optional, or how an empty value behaves despite zero required parameters. The only context offered is the chain (Solana Mainnet), which does not explain the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially the tool name restated plus a network qualifier ('Live Solana Mainnet') and a price tag. It never states in prose what the scanner actually does or returns, and it does not distinguish itself from spread-adjacent siblings like cross-dex-router or orca-whirlpool-scanner.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance at all. The agent is left to infer from the name alone that this tool belongs in SOL/USDC spread analysis rather than any of the other twenty-plus scanners in the catalog.

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