oracle3
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_marketsA | Search open Kalshi or Polymarket markets and return candidates with their best prices. |
| get_marketA | Get one market's details: title, best bid and ask, volume and closing date. |
| get_orderbookA | Get the displayed order book for YES and NO as [price, size] levels, best first. |
| get_quoteA | Get the best bid and ask on YES and NO, in dollars, plus the market's fee schedule. |
| trading_feeA | Compute the venue fee for one fill at a given price and size; a pure calculation with no network calls. |
| check_constraintA | Check offline whether prices you supply violate a no-arbitrage relation, and price the cheapest exploiting basket after fees. |
| check_constraint_liveA | Fetch live quotes and fee schedules for related markets, then check whether their prices violate a no-arbitrage relation after fees. |
| list_relation_typesA | List the relation types the constraint checks support and the probability bound each enforces. |
| fair_valueA | Convert a market price into the probability it implies under the Wang transform, and report the premium. |
| list_relationsA | List the market relations saved on this machine by the oracle3 research CLI, optionally filtered. |
| paper_orderA | Simulate buying YES or NO contracts in the local paper ledger, filling against the live order book with venue fees. Never sends an order to a venue. |
| paper_portfolioA | Show the local paper ledger: cash, open positions and the number of fills. |
| paper_resetA | Erase the local paper ledger and restore the $10,000 starting cash. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes and descriptions cross-reference each other, such as offline vs live constraint checks and orderbook depth vs top-of-book quotes. However, get_quote and get_market both return best bid/ask and fee schedule, so an agent could occasionally confuse them despite the resolution-rules guidance.
All names use snake_case consistently, with predictable prefixes like get_, check_, list_, and paper_. A few tools are noun phrases such as trading_fee and fair_value rather than verb_noun, but the overall convention is coherent.
The 13 tools are well-scoped for prediction-market research and paper trading, covering discovery, pricing, constraint analysis, and ledger operations without obvious redundancy or padding.
The surface covers search, market details, quotes, order books, fees, arbitrage checks, and paper-trade entry, but paper trading only supports buys with no sell, close, or settlement operation. That is a notable lifecycle gap for a trading-oriented server.