MonteWalk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEWSAPI_KEY | No | Your NewsAPI key for news aggregation (optional) | |
| ALPACA_API_KEY | Yes | Your Alpaca API key for paper trading | |
| ALPACA_SECRET_KEY | Yes | Your Alpaca secret key for paper trading |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkB | Returns the health status of the MonteWalk server. |
| get_account_infoB | Get detailed Alpaca account information including equity, buying power, and day trade status. |
| get_priceA | |
| get_fundamentalsC | |
| get_orderbookB | |
| place_orderA | |
| cancel_orderB | |
| get_positionsA | |
| flattenA | |
| get_order_historyC | |
| portfolio_riskB | Returns annualized volatility of the portfolio. |
| varD | Calculates Value at Risk (VaR). |
| max_drawdownB | Calculates Maximum Drawdown. |
| monte_carlo_simulationB | |
| run_backtestA | |
| walk_forward_analysisC | Performs Walk Forward Analysis on MA Crossover. Optimizes (Fast, Slow) on Train, tests on Test. |
| compute_indicatorsC | |
| rolling_statsB | Computes rolling mean and volatility. |
| get_technical_summaryC | Performs a technical analysis summary (RSI, MACD, Moving Averages). Returns a 'Buy', 'Sell', or 'Neutral' signal based on aggregated indicators. |
| mean_variance_optimizeC | Calculates optimal portfolio weights using Mean-Variance Optimization (Max Sharpe). |
| risk_parityC | Calculates weights based on Inverse Volatility (Naive Risk Parity). |
| log_actionA | |
| get_newsB | |
| analyze_sentimentB | |
| get_symbol_sentimentC | |
| add_to_watchlistC | Adds a symbol to the monitoring watchlist. |
| remove_from_watchlistC | Removes a symbol from the watchlist. |
| get_crypto_priceB | |
| get_crypto_market_dataB | |
| get_trending_cryptoB | |
| search_cryptoC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| morning_briefing | Generates a morning briefing prompt with Portfolio and Watchlist context. |
| analyze_ticker | Deep dive analysis prompt for a specific ticker. |
| risk_analysis | Comprehensive risk analysis prompt for the current portfolio. |
| backtest_strategy | Backtesting workflow prompt. |
| crypto_market_update | Cryptocurrency market analysis prompt. |
| portfolio_rebalance | Portfolio rebalancing workflow prompt. |
| sync_watchlist | Intelligent watchlist synchronization with portfolio holdings. Agent automatically adds owned symbols and optionally removes sold symbols. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_portfolio_summary | Returns a live summary of the portfolio from Alpaca (Cash, Positions, Equity). |
| get_watchlist_resource | Returns a live view of the watchlist with current prices. |
| get_news_resource | Returns the latest news headlines for the watchlist. |
| get_crypto_resource | Returns the top trending cryptocurrencies. |
TDQS
Scored across 31 tools
Most tools have distinct purposes, but there is some overlap that could cause confusion. For example, 'get_price' and 'get_crypto_price' both retrieve price data but for different asset classes, and 'analyze_sentiment' and 'get_symbol_sentiment' both handle sentiment analysis with slightly different scopes. The descriptions help clarify, but an agent might misselect between similar tools.
Tool names predominantly follow a consistent verb_noun pattern (e.g., 'add_to_watchlist', 'cancel_order', 'get_account_info'), with only minor deviations like 'flatten' (a verb without a noun) and 'var' (an abbreviation). The naming is readable and predictable overall, though not perfectly uniform.
With 31 tools, the count is excessive for a trading/analysis server, leading to potential bloat. Many tools (e.g., 'max_drawdown', 'rolling_stats', 'var') could be consolidated into broader functions, and the inclusion of placeholders like 'get_orderbook' adds unnecessary complexity. A more focused set of 15-20 tools would be more appropriate.
The toolset covers a wide range of trading and analysis functions, including market data, order management, portfolio analysis, and backtesting. However, there are minor gaps, such as the lack of tools for modifying watchlist entries or handling more advanced order types (e.g., stop-loss). Overall, it supports core workflows effectively with few dead ends.