Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Solana wallet holdings

get_wallet_holdings
Read-onlyIdempotent

Solana wallet holdings: native SOL, SPL tokens with USD values, NFT count (Helius DAS). Costs 0.008 USDC per call (x402, USDC on Solana or Base).

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds critical behavioral context: a per-call cost of 0.008 USDC via x402 (USDC on Solana or Base) and reliance on Helius DAS. This goes beyond annotations and prepares the agent for cost and external dependency, though rate limits or failure modes are not mentioned.

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?

A single, information-dense sentence that front-loads the core functionality and immediately follows with cost and data source. No filler or redundant phrasing—every word earns its place.

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 one simple parameter, an output schema present, and annotations covering safety, the description adds the final missing pieces: cost, payment method, and data provider. An agent has everything needed to decide whether and how to call this tool, and knows what to expect in return.

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?

The schema already describes the wallet parameter as 'Solana wallet address (base58)' with 100% coverage. The tool description does not add any further meaning or formatting hints about the parameter, so it meets the baseline for high schema coverage without enhancement.

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 clearly states the resource (Solana wallet) and the specific data returned: native SOL, SPL tokens with USD values, and NFT count via Helius DAS. It is distinct from the many sibling tools by its precise scope, and the data source is explicitly named.

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 makes the intended use evident (querying wallet holdings) but does not explicitly contrast with alternative tools such as get_wallet_activity or get_token_holdings. It lacks explicit when-to-use or when-not-to-use guidance, though the domain is clear enough to infer basic usage.

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