TapeLog MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAPELOG_DATA | No | Optional path to change where fills are stored. Defaults to ~/.tapelog/fills.json. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| import_fillsA | Import executions from a DAS Trader Trades-window CSV, a Robinhood account activity CSV, or a generic CSV (date,time,symbol,side,qty,price,fees). Pass csv_text or a local file_path. DAS exports have no date: pass trade_date (YYYY-MM-DD). Stored locally (~/.tapelog/fills.json); duplicates are skipped. |
| get_statsB | Stats for closed round trips (optionally between start/end YYYY-MM-DD): net P&L, win rate, profit factor, expectancy, average win/loss, max drawdown, losing streak, hold time, and PDT day-trade count. |
| find_leaksB | Describe where the user's own past results were weakest: time of day, day of week, hold time, symbol, direction, sizing after a loss, and winners vs losers hold time. Descriptive findings only, never trade advice. |
| compare_periodsB | Compare stats between period A and period B (YYYY-MM-DD dates), e.g. last week vs this week. |
| list_tradesC | List reconstructed round trips (most recent first). |
| clear_dataA | Delete all locally stored fills. Requires confirm=true. |
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 6 tools
get_stats, find_leaks, and compare_periods all operate on performance analytics, so an agent might briefly hesitate between them, but each has a clearly stated distinct purpose (general stats vs. descriptive weakness analysis vs. period-vs-period comparison). list_trades, import_fills, and clear_data are unambiguously separate.
Every tool follows a consistent snake_case verb_noun pattern (get_stats, find_leaks, compare_periods, list_trades, clear_data, import_fills). The convention is uniform throughout with no stylistic deviations.
Six tools is well-scoped for a local trade-journaling/analytics server. Each tool covers a distinct operation (import, list, analyze, compare, find weaknesses, reset) and none feels redundant or filler.
The import -> list -> analyze lifecycle is well covered, including a data-reset operation. Minor gaps exist: no way to edit or delete a single misparsed fill, and no export of reconstructed trades, but these are workable around via clear_data plus re-import.