Skip to main content
Glama
michaeljiangmingfeng-debug

quanttogo-mcp-servers

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QUANTTOGO_API_KEYYesAPI authentication key
QUANTTOGO_USER_IDYesYour user ID
QUANTTOGO_API_BASENoAPI endpoint (e.g., https://www.quanttogo.com)

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

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_trading_signalsB

Get latest trading signals from live quantitative strategies. Returns real-time BUY/SELL signals with symbol, quantity, price, and strategy info.

confirm_signalB

Confirm or skip a pending trading signal. EXECUTE will trigger virtual trade execution, SKIP will mark it as skipped.

get_signal_statsC

Get signal statistics and performance metrics for a strategy, including win rate, total trades, and P&L.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
signals-overviewOverview of all active trading signal streams

TDQS

B3.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: confirm_signal handles pending signal actions, get_signal_stats provides performance metrics, and get_trading_signals fetches real-time signals. There is no overlap in functionality, making tool selection unambiguous for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (confirm_signal, get_signal_stats, get_trading_signals), using snake_case and starting with clear action verbs. This predictability aids in understanding and usage.

Tool Count3/5

With only 3 tools, the set feels thin for a trading signal domain, as it lacks operations like creating, updating, or deleting signals, or managing strategies. While core functions are covered, the scope could be expanded for better completeness.

Completeness3/5

The tools cover key aspects: retrieving signals, confirming them, and viewing stats. However, there are notable gaps such as no ability to create or modify signals, manage strategies, or handle trade execution beyond virtual actions, which limits full lifecycle coverage.