Skip to main content
Glama
Sign In
Corvus

Corvus

by Allen-Saji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_recent_transactions

Retrieve recent Solana wallet transactions with parsed human-readable descriptions, timestamps, token transfers, and current USD values.

Instructions

Get recent transaction history for a Solana wallet. Returns parsed transactions with human-readable descriptions, timestamps, and token transfer details. Note: USD values shown are current prices, not prices at time of transaction.

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": {
      "wallet": "<wallet>"
    },
    "name": "get_recent_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of transactions to return (default 10, max 50)
walletYesBase58 Solana wallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses output details (parsed transactions, timestamps, token transfers) and notes that USD values are current prices, not historical. This provides good behavioral context.

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?

The description is two sentences plus a note—efficient and front-loaded. Every sentence adds value without redundancy.

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?

For a tool with no output schema, the description covers return content well (parsed transactions, descriptions, timestamps, token transfers) and adds a note on USD pricing. It is moderately complete for its complexity.

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%, so baseline is 3. The description adds no additional meaning to the parameters beyond what the schema already provides (wallet address, limit).

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 tool gets recent transaction history for a Solana wallet. It uses specific verbs and resources, and the context of sibling tools (balances, prices) distinguishes its purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly indicates when to use this tool (for transaction history) versus siblings (balances, prices). While no explicit when-not is given, the context is clear enough for an AI agent to differentiate.

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

Deploy Server

Other Tools