Skip to main content
Glama
Alubiama
by Alubiama

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
aerodrome_protocol_statusA

Verify official configured Aerodrome contracts, Base block, vote totals, pool count, and the current epoch window at one block.

aerodrome_voting_positionA

Read current veNFT voting power, pool allocations, pool weight shares, gauge liveness, and epoch timing. Uses configured token IDs when none are supplied.

aerodrome_wallet_rewardsA

Read claimable voting rewards for configured veNFT current votes and LP rewards for explicitly configured gauges. Historical vote pools are intentionally not scanned.

aerodrome_wallet_snapshotA

Read protocol, configured veNFT positions, bounded rewards, ETH/AERO/USDC balances and configured lock principal at one Base block, including token display metadata. Recheck the block hash before returning. Preserve PARTIAL status and historical coverage limits.

aerodrome_compare_poolsA

Compare 2–16 distinct pool addresses using official Voter weights, protocol weight shares, gauge registration/liveness and reward contract addresses at one Base block. Preserves input order. Unknown data stays null; no yield, liquidity or profitability ranking.

aerodrome_wallet_changesA

Compare configured voting/rewards plus bounded liquid balances and locks using a caller-generated UUID requestId. Old snapshots without assets initialize the new sections without inferred changes. Reuse the SAME ID for retries: returns the saved report without RPC. A new ID advances the baseline only for a complete snapshot. Report and baseline commit atomically; partial reports are saved without replacing the baseline. This tool writes local history but never changes blockchain state. Missing reward rows are unknown, not zero or proof of claims.

aerodrome_wallet_reportA

Retrieve a committed report by reportId (the original requestId) within the configured wallet scope. No RPC, capture or baseline change. Available after restart and while another capture is running.

aerodrome_wallet_accountingA

Read a bounded Base block page of wallet escrow deposits/withdrawals, selected veNFT rebases and explicit voting-pool reward receipts. Verify protocol logs against successful receipts and matching ERC-20 transfers. Return per-token page sums, event links, gaps and separate holdings at fixed toBlock. Not lifetime discovery, LP accounting, cost basis or net profit. On PARTIAL retry the same page; otherwise continue with nextFromBlock and unchanged scope/toBlock.

aerodrome_wallet_overviewA

Discover up to 16 owned veNFTs directly from the official escrow. Report ETH, escrow-token, USDC and selected token balances, normal locked principal, voting state and bounded rewards at one block. Includes an English brief. No wallet config or manual veNFT IDs needed when wallet is supplied. Preserve partial and managed-position limits; no total net worth or APR.

aerodrome_pool_directoryA

Browse bounded pages of official Voter pool registrations, newest index first, with token pair metadata and gauge state. Registration order is not token listing or pool creation time. Preserve partial rows and pagination coverage.

aerodrome_voting_incentivesA

Read deposited bribes and fees for 1–8 explicit pools at one block. Optionally estimate rewards for additional new votes or full allocation of 1–4 explicit normal veNFTs, subtracting their existing reward-contract weights. Each pool is an independent hypothetical allocation; no ownership/eligibility, claimable reward, guaranteed payout or APR claim. No cross-token value ranking.

aerodrome_reward_planA

Compare 1–3 independent full-veNFT reward allocations in USDC, HOLD_SELECTED or MIXED mode. Retain explicitly selected token addresses; MIXED keepBps applies to each selected token's units. Fetch bounded public Base-token market cards from Dexscreener (token addresses only); includeMarket=false skips this external source. Attach dated client-researched source claims, never automatically verified. Quote direct classic USDC routes at the reward block; no net-after-gas, guaranteed sellability, growth score or execution. Missing research and quotes remain unknown.

aerodrome_compare_allocationsA

Compare 1–4 user-specified basis-point splits across 1–5 explicit pools for 1–4 normal veNFTs using one block. Same split per NFT; subtract existing votes, round per NFT, preserve per-token partial subtotals. Includes hypothetical +20/50/100% competing-vote sensitivity with own votes and deposits fixed; not forecasts. Evidence includes independent full-allocation estimates: use scenarios for split results. No optimizer, USD ranking, eligibility or guaranteed earnings.

aerodrome_decision_cardA

Return an exportable decision card with allocation evidence, sensitivity and content checksum. Default DRAFT. Set selectedScenario and reason only when explicitly chosen by the user. USER_SELECTED is a caller assertion, never a transaction or recommendation. No disk writes; save privately with the local save-card command. Never publish cards.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 14 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but a few pairs could be confused at a glance: wallet_snapshot and wallet_overview both read balances and veNFT positions, and wallet_rewards vs voting_incentives both deal with rewards but for different subjects. The detailed descriptions disambiguate them, but an agent might misselect without careful reading.

Naming Consistency5/5

All tools follow a consistent pattern: the 'aerodrome_' prefix plus descriptive snake_case names. There is no mixing of conventions or vague verbs, and the names clearly hint at the tool's function (wallet_*, compare_*, voting_*, etc.).

Tool Count5/5

14 tools is within the ideal range for a domain-specific server. Each tool covers a distinct aspect of Aerodrome protocol analytics, from pool comparison to wallet accounting to reward planning, and none feel redundant or unnecessary.

Completeness5/5

For a read-only analytics server, the tool surface is remarkably complete: it covers pool data, voting positions, incentives, wallet balances, rewards, historical accounting, snapshots/diffs, reporting, and decision support. There are no obvious dead ends for common analysis workflows, and the tools explicitly note their bounds so agents know what is not included.

Maintenance

ActivityMaintained
ResponsivenessNo issues