Skip to main content
Glama
kukapay

wallet-inspector-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DUNE_SIM_API_KEYYesAPI key obtained from Dune Analytics

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_wallet_balanceA
Query the balance of a specified wallet address across supported EVM and Solana blockchains.

Parameters:
    wallet_address (str): The wallet address to query (e.g., '0x123...' for EVM chains like Ethereum, 
                         Polygon, BSC, or 'DYw8jCT...' for Solana). Must be a valid address for the target chain.

Returns:
    str: Formatted table with balance information (chain, token amount, USD value) for supported chains or an error message.
get_wallet_activityA
Query the activity of a specified wallet address on supported EVM blockchains.

Parameters:
    wallet_address (str): The wallet address to query (e.g., '0x123...'). 
                         Must be a valid EVM-compatible address for chains like Ethereum, Polygon, or BSC.

Returns:
    str: Formatted text with activity information (chain_id, block_time, tx_hash, type, asset_type, value, value_usd) 
         or an error message.
get_wallet_transactionsA
Query the transactions of a specified wallet address on supported EVM and Solana blockchains.

Parameters:
    wallet_address (str): The wallet address to query (e.g., '0x123...' for EVM chains like Ethereum, 
                         Polygon, BSC, or 'DYw8jCT...' for Solana). Must be a valid address for the target chain.
    limit (int): Maximum number of transactions to return (default: 100).

Returns:
    str: Formatted text with transaction information (chain, block_time, tx_hash, from, to, value, value_usd) 
         or an error message.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_wallet_activity focuses on general activity (like transfers, interactions), get_wallet_balance retrieves current token holdings, and get_wallet_transactions fetches detailed transaction lists. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'get_wallet_' as a prefix, followed by a specific noun (activity, balance, transactions). This uniformity enhances readability and predictability across the toolset.

Tool Count3/5

With only 3 tools, the set feels thin for a wallet inspector domain, lacking operations like updating or managing wallets, or querying specific transaction details. While the tools cover basic read operations, the scope is minimal and may limit agent capabilities.

Completeness2/5

The toolset is severely incomplete for a wallet inspector. It only provides read operations (get) without any create, update, or delete capabilities, and misses key functions like analyzing transaction patterns, checking token approvals, or interacting with smart contracts, leaving significant gaps for agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources