Skip to main content
Glama

Trandence Trading Journal

Server Details

Trades, stats, playbooks and notes from your Trandence trading journal. Read-only by default.

Ownership verified

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
32.3% over 56 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

A3.9/5.0

Scored across 17 tools

Disambiguation5/5

Each tool targets a distinct resource or analytical slice—trades, daily rows, symbols, playbooks, setup grades, journal text—and the descriptions explicitly route overlapping questions away from one another. Generic get_breakdown is clearly separated from the specialized breakdowns by saying those have their own tools.

Naming Consistency5/5

All tools follow a snake_case verb_noun pattern, using get for data retrieval, list for enumerations, search for full-text lookup, and write for journal creation. Specialized breakdowns and performance tools share predictable compound names, so the pattern holds across the set.

Tool Count4/5

Seventeen tools is slightly above the typical well-scoped range, but the trading-journal domain justifies the breadth: trade-level, symbol-day, aggregate, risk, discipline, and journal-writing surfaces each need dedicated endpoints. No tool feels redundant; the count is acceptable though on the heavier side.

Completeness4/5

The server covers the full read/analytics surface for trades, performance, playbooks, setups, risk, discipline, and journal lookup, plus journal writing. The main gaps are the lack of CRUD for playbooks/setups/tags and no way to retrieve full journal entries beyond the 31-day window without repeated calls, but these are minor and likely intentional boundaries.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedget_breakdown
  2. 1 tool update
    • Changedget_trades1 field changed
      • addedInput schema / properties / assetType
        Added value: +{
        +  "description": "Only stock trades or only option trades — the Stocks / Options switch in the app. Omit for both.",
        +  "enum": [
        +    "STOCK",
        +    "OPTION"
        +  ],
        +  "type": "string"
        +}
  3. 16 tool updates
    • First observedget_daily_breakdown
    • First observedget_discipline_metrics
    • First observedget_journal
    • First observedget_performance_summary
    • First observedget_playbook_performance
    • First observedget_risk_context
    • First observedget_setup_quality_performance
    • First observedget_symbol_breakdown
    • First observedget_symbol_reviews
    • First observedget_trade_detail
    • First observedget_trades
    • First observedlist_playbooks
    • First observedlist_setups
    • First observedlist_tags
    • First observedsearch_journal
    • First observedwrite_journal_note

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables AI assistants to read and write trading journal data, including trade logs, analytics, psychology audits, risk limits, playbooks, and daily reviews. Provides 38 tools across 7 domains plus workflow prompts for pre-market prep and post-session analysis.
    38
    5 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides read-only access to Trading 212 accounts, enabling AI assistants to retrieve portfolio positions, account summaries, instrument data, and transaction history.
    34 npm
    5
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables local management of Trade Republic accounts, including portfolio, cash, orders, documents, and market data, with dry-run order previews and safety guardrails.
    22
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources