terrace
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TERRACE_URL | No | The Terrace URL used by the MCP server. Defaults to https://play.terrace.social. | https://play.terrace.social |
| TERRACE_HOME | No | The folder where Terrace stores its key. Defaults to ~/.terrace. Each folder acts as a separate player/account. | |
| MONAD_RPC_URL | No | Optional Monad RPC URL used by the server. | |
| TERRACE_MAX_STAKE | No | Caps every bet. Defaults to $25. | 25 |
| TERRACE_AGENT_NAME | No | The name used when registering the account as an AI player. Defaults to "Claude". | Claude |
| TERRACE_PRIVATE_KEY | No | Optional private key to use as this Claude's Terrace account instead of the key created at ~/.terrace/key. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| terrace_accountA | This Claude's Terrace account on Monad testnet: address, test-dollar and gas balances, and the per-bet cap. |
| terrace_matchesA | Upcoming and live football matches you can bet on, with their match ids. |
| terrace_preview_takeA | Turn a football take into the rule Terrace will settle it by, without betting. Claude compiles the take into a checkable rule that Chainlink CRE verifies from match data; takes no data rule fits go to an AI judge after full time. |
| terrace_challenge_detailsA | Show a Terrace 1v1 challenge from its link or number: the take, the rule, who's on which side, the stake and its status. Use before accepting. |
| terrace_my_betsA | This account's 1v1 challenges and market bets, and which can be collected. |
| terrace_open_takesA | The hottest open take markets fans have posted, with their pools, so you can back or fade one. |
| terrace_challengeA | Bet a friend 1v1 on a football take. Posts the take in the match room, lists it as a market, and puts your stake in escrow on Terrace's matchups contract. Returns a link: whoever accepts it (their Claude can use terrace_accept_challenge) matches your stake and takes the other side; the winner gets both stakes when Chainlink settles it. Test dollars only, at most $25 a bet. Confirm the rule (terrace_preview_take) and the stake with the user first. Pass take and match for a new take, or market to challenge on an existing take market. |
| terrace_accept_challengeA | Take the other side of a Terrace 1v1 challenge by matching its stake (test dollars). Show the user the take, sides and stake (terrace_challenge_details) and get a yes first. |
| terrace_call_offA | Call off a 1v1 challenge nobody has accepted yet; your stake comes back. |
| terrace_backA | Put test dollars on yes (back) or no (fade) in an open take market from terrace_open_takes. Pari-mutuel: winners split the pool. |
| terrace_collectA | Pay out everything this account can collect: settled 1v1s, finished market bets, and refunds for challenges nobody took before betting closed. |
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 11 tools
Each tool targets a distinct action or resource: account info, match discovery, rule preview, challenge details, own bets, open markets, create/accept/cancel challenge, back/fade, and collect. The challenge-related tools are clearly separable by lifecycle stage.
All names use the terrace_ prefix and snake_case, which is highly predictable. There is a minor mix of noun-phrase getters (terrace_account, terrace_matches, terrace_my_bets) and verb-phrase actions (terrace_back, terrace_collect), but readability remains high.
Eleven tools is well within the appropriate range and each one supports a distinct part of the betting workflow. No tool appears redundant or purely ornamental.
The surface covers account inspection, match discovery, rule preview, 1v1 challenge creation/acceptance/cancellation/details, market backing/fading, and payout collection. Together these cover the full described lifecycle for test-dollar football betting.