Skip to main content
Glama
0xKoda
by 0xKoda

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
eth_getCodeC

Retrieves the code at a given Ethereum address

eth_gasPriceA

Retrieves the current gas price in wei

eth_getBalanceC

Retrieves the balance of a given Ethereum address

Prompts

Interactive templates invoked by user choice

NameDescription
check-contract
check-wallet
gas-analysis

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: eth_gasPrice retrieves network gas price, eth_getBalance retrieves account balance, and eth_getCode retrieves contract code. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent eth_verbNoun pattern (eth_gasPrice, eth_getBalance, eth_getCode), using snake_case and the same prefix. This predictable naming scheme enhances readability and agent usability without any deviations.

Tool Count2/5

With only 3 tools, this server feels thin for an Ethereum RPC server, as it lacks core operations like sending transactions, querying blocks, or checking transaction status. The count is too low for the apparent scope of Ethereum interaction, limiting functionality.

Completeness2/5

The tool surface is severely incomplete for an Ethereum RPC domain. It includes only read-only queries (gas price, balance, code) but omits essential operations such as eth_sendTransaction, eth_getTransactionByHash, or eth_blockNumber, creating significant gaps that will cause agent failures in typical workflows.

Maintenance

ActivityInactive
ResponsivenessUnresponsive