Skip to main content
Glama

Get the Market Brief

get_market_brief
Read-onlyIdempotent

The Home Market Brief and the reads behind it, by view. brief (default): Gambit's shared written brief of the session (the same for every reader, cached; status 503 while it regenerates). sentiment: the latest CNN Fear & Greed and crypto Fear & Greed readings with CNN's sub-indicators. breadth: the latest market breadth (percent above 20/50/200-day averages, advancers/decliners; market filters it). Its feed is not populated today, so this answers items [] with available false and a note: that is missing data, not a flat market, and CNN's breadth score in view=sentiment (components.breadth of cnn_fear_greed) is the read that exists. equity_changes: latest price (pre-market and post-market included) and change vs the prior session's regular-hours close for US equities/ETFs (symbols). quotes: live value and change for FX pairs, commodities and index ETFs in Twelve Data form (symbols such as EUR/USD, SPY; up to 60). returns: the closes each period is measured from (5d, 1m, 3m, ytd, 1y) — symbols reads US equities, crypto reads Hyperliquid perps; never mix them. series: daily closes for the same two universes over period (default 1m), downsampled to about 90 points; a US equity line ends on its latest price. yields: US Treasury yields. news: the latest headlines from Gambit's news sources (limit 1-30). asset_description: a one-line description of symbol (kind crypto | equity). The response carries app_url, the Market Brief screen. (Requires api:read.)

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_market_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoasset_description only
viewNo
limitNonews only
cryptoNoreturns and series: Hyperliquid perps
marketNobreadth only
periodNoseries only
symbolNoREQUIRED for asset_description
symbolsNoequity_changes, quotes, returns and series (US equities; Twelve Data symbols for quotes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that `brief` is cached and identical for every reader, that it returns status 503 while regenerating, and it pre-empts a real trap by stating the breadth feed is unpopulated and that items [] with available false means missing data rather than a flat market. It also names the auth scope (api:read) and notes where a substitute read lives.

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?

Nearly every clause carries information, and the framing sentence about what the tool is comes first. The cost is structure: ten views are packed into one unbroken paragraph with no list formatting, which makes scanning for a specific view slower than it needs to be.

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 10-way dispatch tool with no output schema and no required parameters, the description covers what each view returns, the one degraded view, and the response's app_url. Minor gaps remain: it does not say what happens if symbols or market are supplied with the wrong view, or how errors other than the 503 manifest.

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?

Schema coverage is already 88%, and the description still adds real meaning: it binds almost every parameter to a specific view (kind for asset_description, limit for news, market for breadth, period for series, crypto/symbols for returns and series), specifies symbol formats (EUR/USD, SPY) and caps (up to 60), notes the default period of 1m, and warns that series lines are downsampled to about 90 points.

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?

Names the resource (the Home Market Brief and its underlying reads) and enumerates each `view` value with a concrete description of the data behind it, so an agent can map a data need to a view. It does not differentiate itself from siblings such as get_sentiment, get_news_headlines, or get_prices, which cover overlapping ground and are never mentioned.

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?

Usage is conveyed implicitly through per-view scoping like 'limit 1-30', 'market filters it', and the hard constraint 'symbols reads US equities, crypto reads Hyperliquid perps; never mix them'. However there is no explicit statement of when to choose this tool over the many overlapping siblings, and no guidance on which views are best for which analytical question.

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