Skip to main content
Glama

FinanceQuery

Price Sparklines

get_spark
Read-onlyIdempotent

Get lightweight close-price sparklines for multiple symbols. Faster and smaller than get_charts — use when you only need price direction/trend across many symbols.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbols": "<symbols>",
      "interval": "<interval>",
      "range": "<range>"
    },
    "name": "get_spark"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesTime range: 1d|5d|1mo|3mo|6mo|1y|2y|5y|10y|ytd|max (default: 1mo)
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolsYesComma-separated list of ticker symbols (e.g., "AAPL,MSFT,GOOG")
intervalYesCandle interval: 1m|5m|15m|30m|1h|1d|1wk|1mo|3mo (default: 1d)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds genuinely new behavioral context not in annotations: it is faster and smaller in payload than get_charts. It does not say what a returned "sparkline" actually looks like (string vs. series), which matters since there is no output schema.

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?

Two short sentences, zero filler, with the core capability stated first and the selection rationale second. Every clause carries information.

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

Completeness4/5

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

For a low-complexity read-only fetch with four fully documented parameters and complete annotations, the description covers purpose and selection adequately. The one residual gap is the shape of the returned sparkline data, which the absent output schema leaves unexplained.

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

Parameters3/5

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

Schema description coverage is 100%, with symbols, interval, range, and fields all documented in-schema, including defaults. The description adds no syntax, format, or constraint detail beyond that, so the baseline 3 is appropriate.

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?

"Get lightweight close-price sparklines for multiple symbols" names a specific verb (get), the exact resource (close-price sparklines), and the scope (multiple symbols). It also contrasts itself with get_charts, so an agent can distinguish the two without opening either schema.

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?

"Use when you only need price direction/trend across many symbols" gives a clear selecting condition, and the comparison to get_charts supplies the alternative. The exclusions are only implied (an agent must infer that get_charts is for full candles), so it falls just short of fully explicit when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.