Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RPC_URLYesAny EVM-compatible RPC endpoint
CHAIN_IDNoChain ID for the network (defaults to 1)1

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
web3_clientVersionB

Returns the current client version

web3_sha3B

Returns Keccak-256 hash of the given data

eth_blockNumberA

Returns the number of the most recent block

eth_getBalanceC

Returns the balance of the account of given address

eth_getTransactionCountB

Returns the number of transactions sent from an address

eth_getBlockByNumberC

Returns information about a block by block number

eth_getTransactionByHashC

Returns the information about a transaction requested by transaction hash

eth_getTransactionReceiptC

Returns the receipt of a transaction by transaction hash

eth_callB

Executes a new message call immediately without creating a transaction

eth_estimateGasC

Generates and returns an estimate of how much gas is necessary

eth_sendRawTransactionC

Creates new message call transaction or a contract creation

eth_gasPriceA

Returns the current price per gas in wei

eth_getCodeC

Returns code at a given address

eth_getStorageAtC

Returns the value from a storage position at a given address

eth_getLogsC

Returns an array of all logs matching a given filter object

eth_chainIdA

Returns the chain ID of the current network

net_versionB

Returns the current network id

net_listeningA

Returns true if client is actively listening for network connections

net_peerCountA

Returns number of peers currently connected to the client

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 19 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap, as they map directly to standard Ethereum JSON-RPC methods. For example, eth_getBalance retrieves account balances, eth_getTransactionByHash fetches transaction details, and web3_clientVersion returns client info, all serving unique functions in the EVM ecosystem.

Naming Consistency5/5

The tool names follow a highly consistent pattern, using prefixes like 'eth_', 'net_', and 'web3_' followed by descriptive, standard method names in snake_case. This uniformity makes the tools predictable and easy to identify, aligning with Ethereum API conventions.

Tool Count5/5

With 19 tools, this server is well-scoped for an EVM interface, covering essential operations such as querying blocks, transactions, balances, network info, and executing calls. The count is appropriate, providing comprehensive coverage without being overwhelming for the domain.

Completeness5/5

The tool set offers complete coverage of core EVM functionalities, including reading data (e.g., blocks, balances, logs), writing transactions (e.g., eth_sendRawTransaction), and utility operations (e.g., gas estimation, hashing). There are no obvious gaps, enabling agents to handle typical blockchain interactions seamlessly.

Maintenance

ActivityStale
ResponsivenessUnresponsive