solana-forensics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HELIUS_API_KEY | Yes | Helius API key for Solana blockchain data access |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| solana_forensics_discoverA | Browse all available Solana forensics operations organized by category. Returns a tree of operations with descriptions. Use this to explore what operations are available before executing them. |
| solana_forensics_get_schemaA | Get detailed parameter schema for a specific operation. Args: operation: Operation identifier in format 'category.action' (e.g., 'forensics.trace_sol_funding', 'forensics.detect_wash_trading') Returns parameter requirements, types, and descriptions. |
| solana_forensics_executeA | Execute a Solana forensics operation with the specified parameters. Use solana_forensics_get_schema first to understand required parameters. Args: operation: Operation identifier (e.g., 'forensics.trace_sol_funding') params: Operation parameters as defined in the schema Returns the operation result. Large results are automatically paginated - use solana_forensics_continue to get next pages. |
| solana_forensics_continueA | Continue retrieving paginated results from a previous operation. Args: session_id: Session ID from the paginated response. If not provided, uses the last paginated operation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct, non-overlapping purpose: discover lists operations, get_schema returns parameter details, execute runs an operation, and continue handles pagination. There is no ambiguity about which tool to use for a given step.
All tools follow a consistent 'solana_forensics_<verb>' pattern (discover, get_schema, execute, continue). The naming convention is uniform and predictable, making the API easy to navigate.
Four tools is well-scoped for a meta-interface. Each tool is necessary for the operation lifecycle (explore, inspect, execute, paginate), and there is no bloat or redundancy.
The tool set covers the full workflow: discovering available operations, fetching schemas, executing them, and continuing through paginated results. No obvious gaps exist for the stated purpose of a forensics operation interface.