Skip to main content
Glama
Sign In

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Solana wallet holdings

get_wallet_holdings
Read-onlyIdempotent

Solana wallet holdings: native SOL with its USD value at AgentFeed's own on-chain SOL price, SPL tokens with mint, symbol and amount (no token prices), NFT count (Helius DAS balances). Costs 0.008 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

NameRequiredDescriptionDefault
walletYesSolana wallet address (base58)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / wallet / maxLength
      Added value: +44
    • addedInput schema / properties / wallet / minLength
      Added value: +32
    • addedInput schema / properties / wallet / 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_wallet_holdings payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_wallet_holdings",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_wallet_holdings",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds significant context beyond annotations: the per-call cost (0.008 USDC), accepted payment networks (x402, USDC on Solana, Base, Polygon, Arbitrum, Arc), and data provenance (AgentFeed's own on-chain SOL price, Helius DAS balances). It also clarifies that token prices are not included.

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?

The description is two sentences with no wasted words: the first lists outputs and limitations, the second covers cost and payment methods. It is front-loaded with the core value and appropriately sized for a paid read tool.

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?

Given the presence of an output schema, annotations covering safety and openness, and full schema coverage for the single parameter, the description is nearly complete. It covers outputs, limitations, cost, and data sources. Minor gaps like rate limits or error behavior are not necessary for this tool type.

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% and the single parameter (wallet) is already well documented with a base58 pattern and description. The tool description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description names a specific verb (get) and resource (Solana wallet holdings) and details exactly what is returned: native SOL with USD value, SPL tokens with mint/symbol/amount, and NFT count. It implicitly distinguishes from sibling tools like get_wallet_activity (activity vs holdings) and get_base_balance (Base vs Solana), but does not explicitly name an alternative.

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?

The description indicates what the tool returns and mentions the cost, but does not state when to use it instead of alternatives such as get_wallet_activity or get_sol_token_check. Usage is implied by the resource name rather than explicitly guided.

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