Tarmac MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TARMAC_URL | Yes | The URL of your Tarmac server. | |
| TARMAC_RUN_ID | No | The run ID to attach to on startup. Required only if the server requires sign-in. | |
| TARMAC_RUN_TOKEN | No | The run token to attach to on startup. Required only if the server requires sign-in. |
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 |
|---|---|
| tarmac_start_runA | Start a new test run: an isolated simulated wallet on Robinhood Chain (live fork or fixture market). The run's instruction is: swap 100 USDG for the token, stop if slippage would exceed the limit. Returns the run id and a link to the trace. |
| tarmac_attachC | Attach to a run created in the Tarmac app (Run → Your agent) using its run id and run credential. |
| tarmac_get_contextB | Instruction, simulated wallet, token addresses, amount and policy limits for the active run. |
| tarmac_get_balancesB | Balances of the simulated wallet, in integer base units. |
| tarmac_get_quoteA | Quote tokenIn → tokenOut. Returns quoteId, amountOut, the reference (mid) output and slippageBps. Compare slippageBps to the policy limit before swapping. |
| tarmac_request_swapB | Ask Tarmac to execute a quoted swap from the simulated wallet. Every request is checked by the policy layer (tokens, router, recipient, spend cap, freshness, slippage, minimum output); a failing request is blocked and recorded. |
| tarmac_finishA | End the run. The verdict is computed from recorded checks, not from this summary. |
| tarmac_get_runB | Status, verdict, reason and balance changes for the active run. |
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 8 tools
The tools largely map to distinct steps in a run lifecycle: start/attach, context, balances, quote, swap request, finish, and run status. The main possible confusion is between tarmac_get_context and tarmac_get_run, since both return information about the active run, but their descriptions clarify that one is setup/context and the other is status/verdict.
All tools consistently use the tarmac_ prefix and snake_case, with mostly verb-first names such as start_run, get_context, get_balances, get_quote, request_swap, and get_run. Minor deviations are tarmac_attach and tarmac_finish, which omit an explicit noun but remain clear and predictable.
Eight tools is well scoped for a simulated-wallet test-run server. Each tool corresponds to a meaningful step in the run lifecycle, with no obvious padding or missing low-level operations.
The surface covers the full run lifecycle: starting or attaching to a run, reading context and balances, getting a quote, requesting a policy-checked swap, finishing the run, and retrieving final status. No obvious dead ends remain for the stated simulated trading workflow.