SVM-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Name | Description |
|---|---|
| get-soon-testnet-balanceC | Get the balance of a address on the Soon testnet |
| get-soon-testnet-last-transactionB | Get the last transaction of an address on the Soon testnet |
| get-soon-testnet-account-tokensC | Get the tokens of a address on the Soon testnet |
| get-soon-mainnet-balanceC | Get the balance of a address on the Soon mainnet |
| get-soon-mainnet-last-transactionC | Get the last transaction of an address on the Soon mainnet |
| get-soon-mainnet-account-tokensC | Get the tokens of a address on the Soon mainnet |
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 6 tools
Each tool has a clearly distinct purpose based on the combination of network (mainnet vs. testnet) and data type (tokens, balance, or last transaction). There is no overlap or ambiguity between tools, as they target specific resources and actions.
All tool names follow a consistent verb_noun pattern with 'get' as the verb, followed by the network and resource (e.g., get-soon-mainnet-account-tokens). The naming is uniform across all tools, using kebab-case consistently without any deviations.
With 6 tools, the server is well-scoped for querying blockchain data on two networks. Each tool earns its place by covering essential data types (tokens, balance, transactions) for both mainnet and testnet, avoiding redundancy or excessive complexity.
The tool set provides comprehensive read operations for blockchain addresses, covering tokens, balance, and last transactions on both mainnet and testnet. A minor gap exists in the lack of write operations (e.g., sending transactions) or broader query capabilities, but the read surface is complete for its apparent domain.