tas-guard
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_infoB | Demo paper account: cash, equity and buying power. |
| get_stock_latest_quoteB | Simulated latest quote for a symbol (demo prices). |
| get_all_positionsB | Open positions in the demo account. |
| get_ordersC | Orders in the demo account. |
| place_stock_orderA | [TAS Guard: max 2000 USD per order, 5000 USD per day; orders over 1000 need human approval] Place a demo stock order. Market orders fill at the simulated price; limit orders rest until cancelled. |
| cancel_order_by_idC | Cancel one demo order. |
| cancel_all_ordersA | [TAS Guard: needs human approval] Cancel every open demo order. |
| close_all_positionsA | [TAS Guard: needs human approval] Sell every demo position at the simulated price. |
| tas_guard_statusA | TAS Guard: show the trading limits that apply to this connection, today's usage, the kill switch and pending approvals. Read-only. |
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 9 tools
Each tool targets a distinct resource and action: account info, quotes, positions, orders, order placement, cancellation (single and all), position closing, and guard status. No overlapping purposes that could cause misselection.
Mostly consistent snake_case with clear verb_noun patterns (get_*, place_*, cancel_*, close_*). The outlier 'tas_guard_status' is a noun phrase rather than verb_noun, a minor deviation.
9 tools is well within the ideal 3-15 range for a demo trading account with guardrails. Each tool earns its place, covering read operations, actions, and guard status without redundancy.
Core lifecycle is covered: account info, quotes, positions, orders (list, place, cancel one/all), close all positions, and guard status. Minor gaps exist (e.g., get order by ID, close single position, order update), but agents can work around them.