Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PRIVATE_KEYYesYour wallet private key on Base
ALCHEMY_API_KEYYesYour Alchemy API key for Base L2 node 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
contract_auditA

Scan smart contract code for vulnerabilities on Base L2. Returns risk score + findings.

base_gas_estimateA

Get current Base L2 gas prices in Gwei with safe/recommended/fast tiers.

yield_farmA

Scan DeFi protocols on Base for highest yield opportunities. Returns pool name, APY, TVL, risk level.

token_analyzerB

Analyze a token contract for honeypot risks, mint functions, ownership patterns. Returns risk score.

wallet_healthB

Analyze wallet portfolio diversification, token concentration, and recent activity. Returns health score 0-100.

generate_mnemonicA

Generate a secure BIP39 mnemonic phrase.

base_priceB

Get current price of a token on Base L2.

dex_quoteB

Get DEX swap quote on Base L2.

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 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: auditing contracts, getting gas prices, finding yield, analyzing token risks, assessing wallet health, generating mnemonics, fetching prices, and getting DEX quotes. There is no overlap where two tools perform the same function.

Naming Consistency3/5

Tool names are readable but follow mixed conventions: some use verb_noun (generate_mnemonic), some noun_verb (contract_audit), some noun_noun (wallet_health, dex_quote), and some have a base_ prefix while others don't. The pattern is not consistent enough to be predictable.

Tool Count5/5

With 8 tools, the server is well-scoped within the ideal 3-15 range. Each tool covers a necessary aspect of the Base L2 agent domain without redundancy or bloat.

Completeness3/5

The set covers a broad range of analytical and informational operations (audit, gas, yield, token analysis, wallet health, price quotes), but lacks actual transaction execution, wallet address derivation, or balance checks. This creates notable gaps for a complete agent workflow, though the existing tools handle a coherent subset.

Maintenance

ActivitySlowing
ResponsivenessNo issues