Skip to main content
Glama
Sign In

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Solana token trade flow

get_sol_token_flow
Read-onlyIdempotent

Use when an agent needs to know who is trading a Solana token. Returns the unique traders over its latest swaps, top-5 share of volume, round-trip wallets, share of brand-new buyer wallets and launch-slot bundle size for mints under 7 days. Costs 0.008 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

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": {
      "mint": "<mint>"
    },
    "name": "get_sol_token_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesthe SPL token mint address
swapsNoswaps to read, 20-100, default 50; a 20 second budget may return fewer, flagged truncated

Output Schema

NameRequiredDescriptionDefault
dataYesthe get_sol_token_flow payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_sol_token_flow
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / swaps / maximum
      Added value: +100
    • addedInput schema / properties / swaps / minimum
      Added value: +20
    • changedInput schema / properties / swaps / type
      Previous value: -"number"New value: +"integer"
  2. Changed3 schema fields changed
    • addedInput schema / properties / mint / maxLength
      Added value: +44
    • addedInput schema / properties / mint / minLength
      Added value: +32
    • addedInput schema / properties / mint / pattern
      Added value: +"^[1-9A-HJ-NP-Za-km-z]{32,44}$"
  3. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-annotation context: a hard cost of 0.008 USDC per call and the accepted payment chains (x402). It stops short of describing latency/truncation behavior, which lives only in the schema.

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?

Two tightly packed sentences: trigger first, then the concrete outputs, then the cost. No filler, and the most decision-relevant information (when to use, price) is front-loaded.

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?

An output schema exists, so return values need not be explained, yet the description still names the key metrics. Combined with cost, trigger, and the mint-age caveat, an agent has everything needed to decide and invoke correctly.

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%, with both 'mint' (SPL mint address) and 'swaps' (20-100, default 50, truncation note) fully documented in the schema. The description adds no parameter-level detail beyond the '<7 days' mint-age caveat that qualifies the bundle-size output.

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 question it answers ('who is trading a Solana token') and enumerates the exact metrics returned: unique traders, top-5 volume share, round-trip wallets, new-buyer share, bundle size. This clearly separates it from holder/check siblings like get_token_holders, get_sol_holder_clusters, and get_sol_token_check.

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?

Opens with an explicit 'Use when' trigger tied to a concrete agent need, and qualifies the bundle-size metric to mints under 7 days. It does not name any alternative tool or state when another tool should be preferred instead.

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

All AgentFeed 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