Skip to main content
Glama
Sign In

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Solana wallet activity

get_wallet_activity
Read-onlyIdempotent

Solana wallet activity: recent transactions for any address, each with the wallet's SOL and token balance changes, the fee, failures and the programs invoked. Read from the chain and summarised by us. Costs 0.02 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

NameRequiredDescriptionDefault
limitNotx count, 1-25, default 10
walletYesSolana wallet address (base58)

Output Schema

NameRequiredDescriptionDefault
dataYesthe get_wallet_activity payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_wallet_activity
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_activity payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_wallet_activity",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_wallet_activity",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  3. 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, open-world, so the safety profile is covered. The description adds genuinely non-obvious context: data is chain-sourced but summarised by the provider, and each call costs 0.02 USDC via x402 with the accepted payment chains listed. It does not mention rate limits or what happens if payment fails.

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, front-loaded with the core capability and followed by a compact cost/payment disclosure. No filler or restatement of the name.

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 the description needn't explain return fields, and the pricing/payment model is disclosed. The remaining gap is operational: no note on error or payment-failure behavior or result volume beyond the limit param.

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% (wallet base58 with pattern, limit 1-25 default 10), so the schema carries parameter meaning. The description adds nothing about either parameter; baseline 3 applies.

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?

States a specific verb and resource ('recent transactions for any address') and enumerates what each entry contains: balance changes, fee, failures, programs invoked. That level of detail distinguishes it from the balance-oriented sibling get_wallet_holdings, although the sibling is never named explicitly.

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?

Usage is implied by 'recent transactions for any address', but there is no explicit guidance on when to prefer this over get_wallet_holdings or the other Solana tools (get_sol_token_flow, get_sol_holder_clusters). The agent must infer the split between activity history and holdings.

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