Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Solana wallet activity

get_wallet_activity
Read-onlyIdempotent

Solana wallet activity: recent transactions for any address, parsed human-readable — type, protocol, description, fee and failures. Helius enhanced transactions. Costs 0.02 USDC per call (x402, USDC on Solana or Base).

Input Schema

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

Output Schema

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

TDQS

A4/5.0
Behavior4/5

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

The annotations already cover read-only/idempotent/non-destructive behavior. The description adds genuinely useful context beyond those annotations: a hard per-call cost (0.02 USDC via x402), the source (Helius enhanced transactions), and that output is parsed human-readable including fees and failures. This materially informs an agent whether to call the tool and what to expect.

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 with the core purpose front-loaded followed by the billing detail; no filler or redundant schema restatement. Every sentence earns its place.

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 a complete schema, output schema, and annotations, the description fills the remaining gaps: cost, payment rail, and data source. 'Recent' is not precisely time-bounded, but the output schema and limit parameter make this acceptable for selecting and invoking the tool correctly.

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%: wallet and limit are already described with address format, range, and default. The description adds no new parameter semantics beyond 'any address', so a baseline score of 3 is appropriate.

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 the resource ('wallet activity') and the specific verb/scope: 'recent transactions for any address', parsed into human-readable fields (type, protocol, description, fee, failures). It is distinct from sibling tools like get_wallet_holdings because it targets transaction history rather than asset balances.

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 conveys that the tool is for any Solana address's recent transaction history, so an agent can infer when to use it. However, it does not explicitly state when not to use it or name a sibling alternative (e.g., get_wallet_holdings for balances), leaving the routing decision mostly implicit.

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