solana-mcp-server

Recent activity

recent_activity

Read-only

Retrieve recent transaction signatures for a Solana address to inspect wallet, token account, or program activity; supports limits and pagination for older results.

Instructions

Returns the most recent transaction signatures that touched an address, newest first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "recent_activity"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of signatures to return (1-100)
`before`	No	Pagination cursor: only return signatures older than this one
`address`	Yes	Base58 address (wallet, token account or program)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful ordering context ('newest first') and clarifies the return payload is signatures rather than full transactions, but it omits whether results span all commitment levels, are cached, or need follow-up calls.

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 sentence with no filler, and the key scoping information ('newest first', 'touched an address') is front-loaded. Nothing in it is redundant.

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?

There is no output schema, and the description does disclose the return payload shape at a high level (signatures, newest first), which is the most important missing piece. It could go one step further and note that full transaction details require get_transaction, but it is essentially complete for a list-style read tool.

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%, so 'address' (wallet, token account or program) and the 'before' pagination cursor are already fully documented. The description's phrase 'touched an address' reinforces that it is not just sender/recipient but any touch, but adds little beyond the schema text.

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 ('Returns') and resource ('most recent transaction signatures') plus a scope ('touched an address, newest first'). It implicitly contrasts with get_transaction (full transaction retrieval), but it never names a sibling tool to make the distinction explicit.

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 'most recent transaction signatures that touched an address' — the agent can infer this is for activity lookups. However, there is no explicit statement of when to prefer this over get_transaction or how to chain with it to get full transaction details.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server