Skip to main content
Glama
Sign In
MyLinedChart Chart Context MCP Server

MyLinedChart Chart Context MCP Server

by none298-dotcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_chart_context

Retrieve the current chart context and workspace summary, including symbol, timeframe, range, provider, connection state, and data freshness from MyLinedChart.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_chart_context"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden. It explicitly states 'Read-only,' which is a key behavioral trait. However, it does not disclose other aspects like authentication needs or behavior when no chart is loaded, though for a simple read-only operation this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that front-loads the purpose, lists key return fields, and appends 'Read-only.' Every word earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description fully explains what the tool returns and its read-only nature. The sibling tools cover separate concerns, so this description is complete for its intended use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters (0 params, 100% schema description coverage trivially). The description adds value by explaining what the tool returns, which is beyond the empty schema. Baseline for 0 params is 4, and the description meets that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description begins with 'Returns the current MyLinedChart chart and workspace summary' which clearly states the verb and resource. It lists specific fields (symbol, timeframe, etc.) and is distinct from sibling tools that return specific data types like candles, drawings, indicators, or provider status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies this tool is for getting a broad snapshot of the current state, it does not explicitly state when to use it versus alternatives like get_candles or get_drawings. No when-not or conditions for use are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools