Skip to main content
Glama
Sign In

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Top token holders

get_token_holders
Read-onlyIdempotent

Top holders of any SPL token: per-account share with top-1, top-5 and top-10 concentration for a Solana mint. A deeper cut than the summary in /api/token-risk. Costs 0.02 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

NameRequiredDescriptionDefault
mintYesSPL token mint address (base58)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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}$"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_token_holders payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_token_holders",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_token_holders",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds genuinely non-derivable context: a 0.02 USDC per-call charge via x402, payable on five named chains. That payment requirement is exactly the kind of operational fact an agent must know before calling. It stops short of disclosing result limits or failure modes.

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 sentences, both earning their place: the first defines scope and output, the second differentiates and discloses cost. Everything is front-loaded with zero filler.

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 an output schema present, return values need not be re-explained, and annotations plus the cost disclosure cover the operational side. The only real gap is how many holders are returned and whether concentration is computed over circulating supply — minor omissions for a one-parameter read tool.

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 coverage is 100% and the single parameter carries its own base58 pattern and description, so the schema does the work. The description only reinforces that the mint is a Solana SPL token, which is mildly useful context but not new semantics. Baseline 3 applies.

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 ('Top holders of any SPL token'), then names the exact metrics returned (per-account share, top-1/5/10 concentration) and the chain (Solana mint). It also distinguishes itself from the risk-summary sibling: 'A deeper cut than the summary in /api/token-risk.'

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 one comparative cue ('deeper cut than /api/token-risk') and a price signal that helps a cost-sensitive agent decide, but it never says when to pick this over the closest siblings like get_sol_holder_clusters, get_sol_token_check, or get_token_metadata. Usage is implied rather than prescribed.

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