Skip to main content
Glama

solana-wallet-intel

by app.vercel.solana-wallet-intel-phi
OverviewDiscussionsAdmin

token_trending

Read-onlyIdempotent

Call this when you need the Solana memecoins traders are watching and a rug-check before you buy, swap, or recommend one. The list includes liquidity, market cap, pair age, 5m/1h/24h price and volume, buy/sell ratio, pump.fun bonding or graduation, and links to pump.fun, DexScreener, and Solscan. Each token has a one-line verdict, riskScore (0 clean to 100), riskLevel (low, medium, high, or unknown), and a risk breakdown with evidence and confidence: top-10 share, mint and freeze authority, LP lock percent, and sniper or bundle share of early supply. riskLevel is unknown when the holder, authority, LP, and sniper checks are all unread, and maxRisk leaves those tokens out. Holder percent falls back to the public RugCheck report at medium confidence when the public RPC cannot list the largest accounts. A successful RPC holder read is kept. Holder-concentration change over 5m/1h/24h is filled when this process has seen the mint before. A check that cannot be read says so, uses low confidence, and is not flagged. On-chain safety flags are plain-English sentences that fire when the top 10 holders own 50% or more, mint or freeze authority is still active, LP is unlocked, or snipers and bundled wallets took 20% or more of early supply. Market flags are short codes: low_liquidity, thin_volume, newly_launched, extreme_move, wash_suspect, paid_boost. Thin, new, and wash-like books are ranked down. The summary block counts tokens by risk level and names the top movers. limit is an integer from 1 to 25 and defaults to 15. minLiquidity is an optional USD floor. maxRisk is low, medium, high, or an integer from 0 to 100. Costs $0.005 USDC (5000 base units) via x402. The same price is charged for HTTP GET /token/trending. An unpaid HTTP call returns 402 even when the query is missing or invalid. A signed call with invalid arguments is rejected before settlement and is not charged. A successful result can set cached, stale, and cacheAgeMs. stale true means a previous result was served while a refresh runs or the upstream failed. You are charged only when the tool result is not an error.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tokens to return. Integer from 1 to 25, or a numeric string. Default 15.
maxRiskNoOptional maximum risk. low, medium, high, or an integer from 0 to 100.
minLiquidityNoOptional minimum pool liquidity in USD. Tokens with unknown liquidity are left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / maxRisk
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "low",
+        "medium",
+        "high"
+      ],
+      "type": "string"
+    },
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Optional maximum risk. low, medium, high, or an integer from 0 to 100."
+}
    • addedInput schema / properties / minLiquidity
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 1000000000000,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "pattern": "^\\d+(\\.\\d+)?$",
+      "type": "string"
+    }
+  ],
+  "description": "Optional minimum pool liquidity in USD. Tokens with unknown liquidity are left out."
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "maximum": 25,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "pattern": "^\\d+$",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / limit / description
      Previous value: -"1 to 25, default 15"New value: +"How many tokens to return. Integer from 1 to 25, or a numeric string. Default 15."
    • removedInput schema / properties / limit / type
      Removed value: -"string"
  3. Changed3 schema fields changed
    • removedInput schema / properties / limit / maximum
      Removed value: -25
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"string"
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the x402 pricing ($0.005 USDC), the 402-on-unpaid-call behavior, that invalid signed calls are rejected before settlement, caching semantics (cached/stale/cacheAgeMs), and the exact fallback paths for holder and risk checks. It also explains how riskLevel becomes 'unknown' and what maxRisk excludes — none of which is derivable from annotations or schema.

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?

The purpose and invocation trigger are front-loaded, which is good, but the description runs as one dense block covering flags, fallbacks, pricing, and cache behavior. Most sentences are relevant, yet the risk-field enumeration and flag lists could be tightened considerably.

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?

With no output schema, the description does the necessary work of describing returned fields (riskScore, riskLevel, risk breakdown, flags, summary block) and the pricing/caching envelope. It covers everything an agent needs to call and interpret the tool; only minor gaps like empty-result behavior remain.

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 the schema already documents limit, maxRisk, and minLiquidity. The description adds a little meaning (maxRisk drops tokens with unread risk checks) but mostly restates bounds and defaults, so it sits at the baseline for full schema coverage.

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 first sentence states a specific resource and verb: the Solana memecoins traders are watching plus a rug-check before buying, swapping, or recommending. That distinguishes it cleanly from the wallet_* siblings, which operate on wallets rather than token lists.

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?

"Call this when you need the Solana memecoins traders are watching and a rug-check before you buy, swap, or recommend one" gives a clear triggering context. It stops short of explicit when-not guidance or naming alternatives, though no close sibling alternative exists among the listed tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All solana-wallet-intel toolsInspect
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