Skip to main content
Glama

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

TableJSON Schema
NameRequiredDescriptionDefault
walletYesSolana wallet address (base58)

Output Schema

TableJSON 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. 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"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, but the description adds critical context the annotations cannot: a per-call cost of 0.008 USDC, the x402 payment rails (USDC on Solana, Base, Polygon, Arbitrum, Arc), and the provenance of the data (AgentFeed's own on-chain SOL price, Helius DAS). It does not cover auth setup beyond payment or rate limits, so it stops short of a 5.

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?

A single front-loaded sentence that leads with the resource and then unpacks contents, caveats and cost. Every clause carries information, though the parenthetical stacking makes it dense to parse in one pass.

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?

With an output schema present, return-value detail is not strictly required, yet the description still characterizes the payload and discloses the paid-call cost an agent must account for before invoking. Nothing essential for correct invocation is missing.

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% for the single 'wallet' parameter, so the schema already documents the base58 Solana address format. The description adds no parameter-level detail beyond that, which matches the baseline 3 when the schema carries the weight.

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 description names a specific resource (Solana wallet holdings) and enumerates exactly what is returned: native SOL with USD value, SPL tokens with mint/symbol/amount, and NFT count. The Solana scoping also cleanly separates it from Base-chain siblings such as get_base_balance.

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is named, even though get_wallet_activity and get_sol_token_check are close siblings. The 'no token prices' caveat hints at a limitation but never points the agent to the tool that does supply prices.

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