Skip to main content
Glama

Manawa Terminal

Search financial data

finance_search
Read-only

Search financial data and return an answer with an inline widget.

Covers stocks, macro, forex, crypto, commodities, earnings, technicals,
and related market questions. Pass the user's question in `query` without
rephrasing.

To screen a named watchlist or portfolio, call list_watchlists or
list_portfolios first, then pass the symbols here with filter criteria in
`query`.

Exclusive modes when a Deep Dive exists:
  focus=ai + section=… → narrative section
  focus=raw + source=… → thin data slice
  focus=catalog → list available Deep Dives

Args:
    query: The user's financial question
    symbols: Optional ticker universe to screen (e.g. from list_watchlists)
    section: Optional Deep Dive section (competition, valuation, thesis,
        forecast, analyst_consensus, people, financials, earnings,
        technicals, overview, moves, markets, flow, calendar, catalysts, odds)
        or raw tapes: options, buzz, acceleration, heatmap, etf, bonds.
        The ETF board is section=etf with no ticker. One fund's holdings
        are section=etf plus that ticker. The bond board is section=bonds.
        A TIPS yield labeled real is the real yield. A spread marked n/a
        stays n/a. Do not use an option-adjusted spread as the page spread.
        Thesis is section=thesis and opens /stock/T/thesis.
        Business is section=competition (/stock/T/competition).
        Price is /stock/T/overview; Large Moves on that tab are section=moves.
        Forecast narrative is section=forecast (/stock/T/analysis).
        Street targets and stance are section=analyst_consensus (/stock/T/valuation).
        Dividends, buybacks, and the alignment / allocation boxes are
        section=financials. There is no Capital section.
        Buzz, social media, reddit, twitter, sentiment, or what people are
        talking about MUST be section=buzz. Do not send those to news or
        catalysts. Consumer sentiment and analyst sentiment are not Buzz.
        Stocks accelerating, price acceleration, speeding up, or speeding
        down MUST be section=acceleration. Do not send those to movers.
        Revenue, earnings, and growth acceleration are not this board.
        Advance/decline, names within 10% of the 52-week high or low, or
        the market P/S, P/E, and P/FCF medians MUST be section=heatmap.
        Do not send those to the sector treemap. One company's P/E is not
        this row.
        One name's options, realized vol, vola, call or put volume, or
        call or put premium MUST be section=options. The 21-day realized
        vol is a yearly rate that places the percentile strikes. A band
        word compares today's session with the prior 20 sessions.
        A press release, presentation, 10-Q, or 10-K for one ticker is
        section=earnings, focus=raw, source=earnings_documents. That is
        not the Earnings write-up.
        Stocks Flow lines are Insiders, Politicians, Institutional, and
        Large Holders. Pass those questions verbatim and do not set
        section=flow. section=flow is only the Flow Deep Dive. Open,
        Increase, Decrease, and Close are the four moves. A politician
        Purchase is an Increase and a plain Sale is a Decrease; an
        asterisk means the form did not say. Institutional ETFs and
        Stocks are a listing. Latest, Largest, and Best are gone. Large
        Holders is 13D and 13G. Do not invent a dollar value there.
    focus: Optional exclusive mode: ai | raw | auto | catalog
    source: Optional thin raw slice when focus=raw (comparison_peers,
        price_targets, consensus, quote, key_financials,
        earnings_documents, …)
    strategy_id: Optional strategy UUID from list_strategies. When set,
        this search is tagged on that strategy's activity.

Input Schema

NameRequiredDescriptionDefault
focusNo
queryYes
sourceNo
sectionNo
symbolsNo
strategy_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / strategy_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Strategy Id"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, open-world, non-destructive search. The description adds meaningful behavioral context beyond the annotations, including that it returns an answer with an inline widget and that focus modes are exclusive when a Deep Dive exists, though it omits auth, rate-limit, and fallback behavior.

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

Conciseness2/5

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

The first sentence is front-loaded, but the description is extremely long and rambling, with large blocks of edge-case routing rules, repeated MUST/Do not instructions, and inconsistent formatting. Important information is present but poorly structured and not concise.

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 six-parameter open-world tool with no output schema and 0% schema description coverage, the description supplies a lot of missing context about modes and sections. It remains incomplete on default behavior for focus=auto, the exact return shape beyond an inline widget, and when to choose this tool over several 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 description coverage is 0%, so the description must carry parameter semantics, and it does document all six parameters. The section parameter is given extensive value mappings and routing rules, though the prose is difficult to parse and some enumerations are incomplete or buried.

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 specific verb and resource: search financial data and return an answer with an inline widget. It names covered domains (stocks, macro, forex, crypto, etc.) but does not clearly differentiate itself from many siblings such as run_screener, run_deepdive, or earnings_rag.

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?

It gives substantial usage context, including passing the user's question verbatim, calling list_watchlists or list_portfolios before screening, and exclusive focus modes. However, the guidance is oriented toward section routing and does not clearly explain when to use this tool instead of sibling tools like run_screener or earnings_rag.

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