Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPINION_API_KEYYesYour Opinion.trade API key (required for all operations)
OPINION_CHAIN_IDNoNetwork chain ID (56=BNB mainnet, 97=BNB testnet)56
OPINION_PRIVATE_KEYNoYour Ethereum private key for trading mode (optional, enables trading capabilities with EIP712 signing)

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
get_marketsC

List prediction markets with filtering options (limit, offset, status)

get_market_detailsC

Get detailed information about a specific market by ID

get_token_priceC

Get current price for a specific token/outcome

get_orderbookC

Get order book (bids/asks) for a token

get_price_historyC

Get historical price data (OHLCV) for a token

search_marketsC

Search markets by keyword or phrase

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity: get_market_details focuses on a specific market, get_markets lists markets, get_orderbook shows bids/asks, get_price_history provides historical data, get_token_price gives current price, and search_markets enables keyword search. The descriptions reinforce these distinct roles, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case (e.g., get_market_details, get_orderbook, search_markets). The naming is predictable and readable throughout the set, with no deviations in style or convention.

Tool Count5/5

With 6 tools, the count is well-scoped for a prediction market server, covering core functionalities like listing, searching, and retrieving market and price data. Each tool earns its place without feeling excessive or insufficient for the domain.

Completeness4/5

The tool surface provides strong coverage for querying and analyzing prediction markets, including market details, listings, order books, and price data. A minor gap exists in the lack of tools for creating or trading on markets (e.g., place_order, create_market), but agents can still perform comprehensive read-only operations effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues