Skip to main content
Glama

Get symbol research

get_symbol_research
Read-onlyIdempotent

The Research page's reads for one symbol, by view. snapshot (default): the stored fundamentals and trading statistics for an equity (Databento). bars: OHLCV bars for the chart (interval 1m | 5m | 15m | 30m | 1h | 1d | 1w, required start / end ISO timestamps, optional max_points); status pending (HTTP 202) means the series is still being prepared — retry shortly. return: the return between two timestamps — venue reference (US equities) or hyperliquid (perps, bare or dex-prefixed), start and end timezone-aware ISO timestamps with start < end <= now. trade_baseline: the exact first trade at or after observed_at (US equities). context: the research context sections Gambit assembles for the symbol (price action, flows, news and the providers behind each; interval and window as for bars; an X post in recent_headlines carries its url and authorUsername with title null, not the post's text). relationship_profile: the curated relationships Gambit uses to match news to this symbol (same exposure, entity names, cross-listings, topics, with evidence). The same for every reader. The response carries app_url, the Research page for the symbol. (Requires api:read.)

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": {
      "symbol": "<symbol>"
    },
    "name": "get_symbol_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoISO timestamp: context; REQUIRED for bars and return
viewNo
startNoISO timestamp: context; REQUIRED for bars and return
venueNoREQUIRED for return
symbolYes
intervalNobars and context
max_pointsNobars and context
observed_atNoREQUIRED for trade_baseline: timezone-aware ISO timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / end / description
      Previous value: -"ISO timestamp: bars, context; REQUIRED for return"New value: +"ISO timestamp: context; REQUIRED for bars and return"
    • changedInput schema / properties / start / description
      Previous value: -"ISO timestamp: bars, context; REQUIRED for return"New value: +"ISO timestamp: context; REQUIRED for bars and return"
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses an async state (status pending with HTTP 202 means the series is still preparing, retry shortly), an auth scope (requires api:read), a response hint (app_url points to the Research page), and a non-obvious data shape (an X post in recent_headlines carries url and authorUsername with title null, not the post text). Those are behaviors an agent could not get from the annotations or schema.

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?

No filler sentences and the default view is front-loaded, followed by the view-by-view breakdown. The telegraphic style ('bars: ... status pending (HTTP 202) means ...') makes it dense to parse, but 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?

With eight parameters and no output schema, the description carries the return-shape burden and does explain what each view yields, including the app_url field and the pending/202 case. It is complete enough to call correctly; the only material gap is guidance against overlapping sibling tools.

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?

Schema coverage is 75%, so the schema already covers much of this, yet the description adds conditional meaning the schema only hints at: which params are required per view, and that venue semantics differ (reference for US equities, hyperliquid for perps, bare or dex-prefixed). That compensation for the conditional-requirement logic is genuinely useful.

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 states a concrete verb and resource ('reads for one symbol, by view') and enumerates all six views with what each returns, so an agent knows exactly what the tool covers. It stops short of distinguishing itself from siblings like get_bars, get_live_snapshot or get_sentiment, which overlap on the same data.

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?

It gives per-view preconditions clearly (snapshot is the default; start/end required for bars and return; observed_at required for trade_baseline; venue required for return), which is real usage guidance. It never says when to pick this tool over get_bars or get_live_snapshot, so the cross-tool choice is left to inference.

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.

Resources