Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GEXNO_API_BASENoBase URL of the Gexno Web3 API used by the local stdio bundle.https://api.gexno.com
GEXNO_INTERNAL_TOKENNoOnly set this if you run your own Gexno server — never commit it.

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
lookup_walletA

Look up an Ethereum wallet: ETH balance, contract flag, outbound tx count, and simple risk heuristics (ok / new_wallet / contract / eip7702). EIP-7702 delegated EOAs report risk=eip7702. Read-only; not an AML score.

lookup_nftA

Resolve NFT metadata for a contract + tokenId: name, description, image HTTP URL, IPFS gateway link, and raw metadata JSON. Supports ERC-721 and ERC-1155. Read-only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools target clearly distinct resources: an Ethereum wallet lookup versus an NFT metadata resolver. Their descriptions make the boundary unambiguous, with no overlap in purpose.

Naming Consistency5/5

Both names follow the same predictable lookup_noun pattern (lookup_wallet, lookup_nft). The convention is consistent and easy for an agent to infer.

Tool Count3/5

Only two tools are provided, which feels thin for a Web3 server even if the scope is deliberately narrow. Each tool is meaningful, but the surface is borderline minimal.

Completeness2/5

The surface covers wallet summaries and NFT metadata only, leaving obvious Web3 gaps such as transaction lookup, ERC-20/token balances, ENS resolution, or contract data. Agents would frequently hit dead ends for common blockchain queries.

Maintenance

ActivityMaintained
ResponsivenessLimited data