Skip to main content
Glama

get_technicals

Analyze a stock's technicals: trend, momentum, volatility, and key levels, using moving averages, RSI, ATR, relative strength, and drawdown from full-market data, with support/resistance.

Instructions

Technical picture for a symbol: trend, momentum, volatility, key levels.

Computed from daily bars on the consolidated SIP tape, so volume is the
full market rather than a single venue. Returns moving-average structure,
RSI, ATR (with stop-distance guidance), relative strength versus a
benchmark, drawdown from the one-year high, and clustered support and
resistance annotated with what each level does at the current price.

Anything that could not be computed from the available history is null and
explained under `limitations` rather than approximated.

Args:
    ticker: Stock symbol, e.g. "NVDA".
    benchmark: Symbol for relative strength, default "SPY".
    lookback_days: Calendar days of history to pull. 500 gives a 200-day
        moving average enough trading sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
benchmarkNoSPY
lookback_daysNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries the full burden. It transparently explains data source (SIP tape), the fact that volume is full-market, and the null-handling behavior under `limitations`. It lacks explicit read-only confirmation or rate-limit information, but the read-only nature is strongly implied by the tool name and content.

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 well-structured and front-loaded with the purpose. Each paragraph earns its place, covering data source, return contents, null behavior, and parameters. The Args list is concise yet informative, with no repetition of schema defaults.

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 the tool's complexity and the presence of an output schema, the description is thorough. It covers data source, parameter semantics, null handling, and expected return components, making it fully sufficient for an agent to invoke correctly.

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

Parameters5/5

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

The schema has 0% coverage, but the description's Args section provides meaningful explanations for all three parameters, including the role of benchmark and how lookback_days relates to the 200-day moving average. This goes well beyond the bare schema titles.

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?

The description clearly states the tool's purpose as providing a 'technical picture for a symbol' and enumerates specific components (trend, momentum, volatility, key levels). It differentiates from sibling tools like get_financials and get_metrics by focusing on technical analysis from daily bars, with details such as moving-average structure, RSI, and ATR.

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

Usage Guidelines4/5

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

The description implies usage for obtaining daily-bar technicals, emphasizing the consolidated SIP tape and full-market volume, which is useful context. However, it does not explicitly state when to prefer this tool over alternatives or provide exclusions, so it falls short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Saivikaskillamsetty/tradingdesk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server