Skip to main content
Glama

Algo Trade Analytics

by com.algo-trade-analytics.app
OverviewDiscussionsAdmin

Server Details

AI-assisted quantitative research and strategy validation through market context, experiments, backtesting, and walk-forward analysis.

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
5.0% over 25 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

B3/5.0

Scored across 58 tools

Disambiguation2/5

Multiple tools have unclear boundaries, including load_case_study vs ata_load_case_study, ata_research_workflow_status vs ata_get_research_workflow_status, and three separate cancel_research_* variants. Robustness-related tools like analyze_parameter_robustness, analyze_overfit_probability, stress_test_candidate, and walk_forward_candidate also overlap substantially. An agent would frequently need to read full descriptions to avoid selecting the wrong tool.

Naming Consistency3/5

Most tools follow a snake_case verb_noun pattern, which is readable. However, the ata_ prefix is applied inconsistently: some core workflow tools (load_case_study, create_research_run) have duplicate or near-duplicate ata_ prefixed counterparts, and analyze_* is used alongside bare verbs like evaluate, verify, and profile. The pattern is not chaotic but not consistently predictable.

Tool Count2/5

With 58 tools, this is well above the 25+ threshold that signals an overly heavy tool surface. While the research workflow is complex, many tools are variants of status checking, cancellation, or job management that could be consolidated. The count will likely overwhelm agents and increase selection errors.

Completeness4/5

The tool set covers the full research lifecycle: hypothesis creation, protocol definition, baseline profiling, candidate evaluation, robustness testing, evidence maturity, lessons, case studies, and promotion claims. Minor gaps exist, such as no explicit update/delete for hypotheses or case studies, but the core domain appears well covered.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedpropose_strategy_candidate5 fields changed
      • addedInput schema / properties / baselineSource / anyOf
        Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
      • addedInput schema / properties / baselineSource / description
        Added value: +"Pine source the candidate derives from. Omit it, or pass \"platform_benchmark\", to derive from the platform benchmark baseline for the bound scope (EMA 20/50 long-only crossover declaring 1bp commission per side and 2 ticks slippage). Never write your own baseline: a hand-written one with no declared costs is honoured verbatim by every later comparison and fails cost sensitivity."
      • removedInput schema / properties / baselineSource / minLength
        Removed value: -1
      • removedInput schema / properties / baselineSource / type
        Removed value: -"string"
      • changedInput schema / required
        Previous value: -[
-  "baselineSource",
-  "candidateSource",
-  "hypothesis",
-  "changesFromBaseline"
-]New value: +[
+  "candidateSource",
+  "hypothesis",
+  "changesFromBaseline"
+]
  2. 4 tool updates
    • Changedevaluate_candidate5 fields changed
      • addedInput schema / properties / baselineSource / anyOf
        Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
      • addedInput schema / properties / baselineSource / description
        Added value: +"Pine source of the comparison baseline. Omit to use the platform benchmark baseline for this scope, which declares 1bp commission per side and 2 ticks slippage so the comparison is not a costed candidate against a zero-cost control."
      • removedInput schema / properties / baselineSource / minLength
        Removed value: -1
      • removedInput schema / properties / baselineSource / type
        Removed value: -"string"
      • changedInput schema / required
        Previous value: -[
-  "symbol",
-  "timeframe",
-  "startDate",
-  "endDate",
-  "baselineSource",
-  "candidateSource",
-  "protocolId"
-]New value: +[
+  "symbol",
+  "timeframe",
+  "startDate",
+  "endDate",
+  "candidateSource",
+  "protocolId"
+]
    • Changedstress_test_candidate5 fields changed
      • addedInput schema / properties / baselineSource / anyOf
        Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
      • addedInput schema / properties / baselineSource / description
        Added value: +"Pine source of the comparison baseline. Omit to use the platform benchmark baseline for this scope, which declares 1bp commission per side and 2 ticks slippage so the comparison is not a costed candidate against a zero-cost control."
      • removedInput schema / properties / baselineSource / minLength
        Removed value: -1
      • removedInput schema / properties / baselineSource / type
        Removed value: -"string"
      • changedInput schema / required
        Previous value: -[
-  "symbol",
-  "timeframe",
-  "startDate",
-  "endDate",
-  "baselineSource",
-  "candidateSource",
-  "protocolId"
-]New value: +[
+  "symbol",
+  "timeframe",
+  "startDate",
+  "endDate",
+  "candidateSource",
+  "protocolId"
+]
    • Changedverify_candidate5 fields changed
      • addedInput schema / properties / baselineSource / anyOf
        Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
      • addedInput schema / properties / baselineSource / description
        Added value: +"Pine source of the comparison baseline. Omit to use the platform benchmark baseline for this scope, which declares 1bp commission per side and 2 ticks slippage so the comparison is not a costed candidate against a zero-cost control."
      • removedInput schema / properties / baselineSource / minLength
        Removed value: -1
      • removedInput schema / properties / baselineSource / type
        Removed value: -"string"
      • changedInput schema / required
        Previous value: -[
-  "symbol",
-  "timeframe",
-  "startDate",
-  "endDate",
-  "baselineSource",
-  "candidateSource",
-  "protocolId"
-]New value: +[
+  "symbol",
+  "timeframe",
+  "startDate",
+  "endDate",
+  "candidateSource",
+  "protocolId"
+]
    • Changedwalk_forward_candidate5 fields changed
      • addedInput schema / properties / baselineSource / anyOf
        Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
      • addedInput schema / properties / baselineSource / description
        Added value: +"Pine source of the comparison baseline. Omit to use the platform benchmark baseline for this scope, which declares 1bp commission per side and 2 ticks slippage so the comparison is not a costed candidate against a zero-cost control."
      • removedInput schema / properties / baselineSource / minLength
        Removed value: -1
      • removedInput schema / properties / baselineSource / type
        Removed value: -"string"
      • changedInput schema / required
        Previous value: -[
-  "symbol",
-  "timeframe",
-  "startDate",
-  "endDate",
-  "baselineSource",
-  "candidateSource",
-  "protocolId"
-]New value: +[
+  "symbol",
+  "timeframe",
+  "startDate",
+  "endDate",
+  "candidateSource",
+  "protocolId"
+]
  3. 58 tool updates
    • First observedanalyze_bootstrap_confidence
    • First observedanalyze_cost_sensitivity
    • First observedanalyze_cross_scope
    • First observedanalyze_losing_trades
    • First observedanalyze_market_coverage
    • First observedanalyze_overfit_probability
    • First observedanalyze_parameter_robustness
    • First observedanalyze_risk_management
    • First observedanalyze_signal_audit
    • First observedanalyze_trade_features
    • First observedata_cancel_research_job
    • First observedata_cancel_research_task
    • First observedata_cancel_research_workflow
    • First observedata_context
    • First observedata_get_evidence_maturity
    • First observedata_get_prompt
    • First observedata_get_research_contract
    • First observedata_get_research_job_status
    • First observedata_get_research_notebook
    • First observedata_get_research_plan
    • First observedata_get_research_task
    • First observedata_get_research_task_result
    • First observedata_get_research_workflow_status
    • First observedata_get_webhook_router_pattern
    • First observedata_health
    • First observedata_list_case_studies
    • First observedata_list_prompts
    • First observedata_list_research_reports
    • First observedata_list_research_tasks
    • First observedata_list_resources
    • First observedata_load_case_study
    • First observedata_mcp_usage_status
    • First observedata_plan_case_study_hardening
    • First observedata_read_resource
    • First observedata_record_research_task_progress
    • First observedata_research_workflow_status
    • First observedata_resume_research_workflow
    • First observedata_start_research_job
    • First observedata_start_research_run
    • First observedata_start_research_workflow
    • First observedclaim_promotion_state
    • First observedclose_research_experiment
    • First observedcommit_research_lesson
    • First observedcompare_trials
    • First observedcreate_research_hypothesis
    • First observedcreate_research_run
    • First observeddefine_experiment_protocol
    • First observedevaluate_candidate
    • First observedinspect_market_context
    • First observedload_case_study
    • First observedprofile_baseline
    • First observedpropose_strategy_candidate
    • First observedrecall_research_lessons
    • First observedrun_parameter_sweep
    • First observedstage_candidate_for_editor
    • First observedstress_test_candidate
    • First observedverify_candidate
    • First observedwalk_forward_candidate

Publisher details

Operator
Algo Trade Analytics
Operator website
https://algo-trade-analytics.com
Vendor relationship
First-party
Documentation
https://docs.algo-trade-analytics.com/guides/mcp
Trust center
Not applicable
Restrictions
OAuth authorization is required. Access is limited to entitled Algo Trade Analytics accounts and the scopes granted during authorization.

Related MCP Servers

  • Citesurf MCP

    citesurf
    A
    license
    A
    quality
    C
    maintenance
    Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
    16
    24 npm
    1
    MIT
  • industrylens-mcp by IndustryLensOp

    industrylens-mcpofficial

    IndustryLensOp
    A
    license
    Not graded
    quality
    B
    maintenance
    Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
    MIT
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources