Skip to main content
Glama
none298-dotcom

MyLinedChart Chart Context MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MLC_CONTEXT_FILENoOverride the context file path. Example: /custom/path/agent-context.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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_chart_contextA

Returns the current MyLinedChart chart and workspace summary: symbol, timeframe, range, provider, connection state, feed type, candle/drawing/indicator counts, diagnostics ID, and data freshness. Read-only.

get_candlesA

Returns the most-recent OHLCV candle bars for the current chart. Fields: timestamp (epoch ms), open, high, low, close, volume. Read-only.

get_drawingsA

Returns all drawings and price levels for the current chart symbol: trend lines, horizontal levels, note labels, and other overlays. Read-only.

get_indicatorsA

Returns the configured indicators for the current chart: name, calculation parameters, placement (main/lower), and visibility. Does NOT include series data. Read-only.

get_provider_statusA

Returns IBKR connector and market-data provider status: connection state, MarketDataStatus code, feed type (delayed/live), diagnostics ID, and last-updated. Never exposes account IDs, credentials, or bridge URLs. Read-only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect of chart data (candles, context, drawings, indicators, provider status) with no overlap, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tools follow a consistent 'get_<noun>' pattern, using snake_case and clear noun phrases that match their function. No deviations.

Tool Count5/5

5 tools is well-scoped for a read-only chart context server. Each tool serves a clear purpose without excess or redundancy.

Completeness5/5

The set covers all major read-only aspects of chart context: price data (candles), overall context, drawings, indicators, and provider status. No obvious gaps for its intended purpose.

Maintenance

ActivityStale
ResponsivenessNo issues