TradingAgentStack
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Search the TradingAgentStack directory of broker MCP servers, broker/market-data APIs, agent frameworks, backtesters and security tools. Returns short summaries; use get_tool for full details. |
| get_toolA | Full sourced record for one tool: assets, live vs paper, order approval/safety controls, pricing, rate limits, source and last-checked date. |
| compare_brokersB | Side-by-side comparison of two brokers/tools (safety controls, paper trading, pricing, rate limits). |
| list_categoriesA | List directory categories with tool counts. |
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 4 tools
Each tool maps to a clearly distinct action and resource: search summaries, full record retrieval, pairwise comparison, and category listing. The only mild overlap is compare_brokers potentially involving 'tools' as well as brokers, but the description resolves this clearly.
All four names follow a consistent snake_case verb_noun pattern: search_tools, get_tool, compare_brokers, list_categories. The convention is predictable and readable throughout.
Four tools are well-scoped for a read-only directory/lookup server. Search, detail, comparison, and category listing cover the essential browsing workflow without redundancy.
The surface covers the core discovery workflow: finding tools, getting full details, comparing options, and listing categories. Minor gaps exist around direct browse-by-category, filters, or pagination, but agents can work around these via search.