Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

get_quote

Retrieve the latest candle data—open, high, low, close, volume, and time—from the open TradingView chart to support live market analysis.

Instructions

Latest candle (open, high, low, close, volume, time) of 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": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one important trait: the result comes from 'the open chart', implying a dependency on current chart state. It says nothing about behavior when no chart is open, staleness/live-updating of the bar, or error conditions, which are the main risks for a zero-parameter state-dependent read.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler, and the field list is placed immediately after the resource name. It reads as a fragment rather than a complete statement, but nothing is wasted.

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 with no output schema, the description is adequate in stating what data comes back, but it should say what happens when no chart is open and whether the candle is live or last-closed. These gaps matter because the tool's only context is chart state.

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 no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description's field enumeration usefully characterizes the response shape instead.

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

Purpose4/5

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

The description names the specific resource returned (the latest candle) and enumerates its fields (open, high, low, close, volume, time), which implicitly contrasts with the plural get_candles sibling. It lacks an explicit verb and never names an alternative, so it falls short of a 5.

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 guidance on when to call this versus get_candles, save_candles, or set_timeframe, and no stated prerequisites. The agent must infer that this is the lightweight single-bar read from the phrase 'latest candle' alone.

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