Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

chart_health

Checks the open TradingView chart and returns its symbol, timeframe, layout name, and loaded bar count so you can verify chart state before analysis or annotation.

Instructions

Symbol, timeframe, layout name and how many bars are loaded on the open chart.

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": "chart_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations and no output schema are provided, so the description carries the full burden. It does disclose the returned data (symbol, timeframe, layout name, bar count), which is genuinely useful since no output schema exists, but it never states that the call is read-only, side-effect free, or how the values are formatted.

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

Conciseness3/5

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

It is a single short fragment with no wasted words, but it is not a grammatical sentence and leads with a bare field list rather than an action, making it feel like an unfinished schema annotation.

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

Completeness3/5

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

For a zero-parameter read tool with no annotations and no output schema, the description usefully substitutes for a return-value spec. However, it omits any statement of what the tool does or when to call it, so it is only minimally complete.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description's field list is about outputs, not inputs, so no parameter meaning is lost.

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

Purpose3/5

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

The description is a noun-phrase field list ('Symbol, timeframe, layout name and how many bars are loaded') with no verb, so the agent must infer from the name chart_health that this reports open-chart state. The listed fields do make clear it is chart-level metadata rather than candles or quotes, which distinguishes it loosely from get_candles and get_quote, but the purpose is implied rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_quote or get_candles. The agent can only guess that this is a 'check current chart configuration' call from the field list.

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