Skip to main content
Glama

Manawa Terminal

by app.manawa
OverviewDiscussionsAdmin

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.
        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.
    focus: Optional exclusive mode: ai | raw | auto | catalog
    source: Optional thin raw slice when focus=raw (comparison_peers,
        price_targets, consensus, quote, key_financials, …)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
focusNo
queryYes
sourceNo
sectionNo
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the exclusive-mode semantics, that it returns a rendered answer/widget rather than raw data, and the interplay between focus, source and section. It stops short of describing result shape or any limits.

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

Conciseness3/5

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

Front-loaded with the core purpose, but the Args block balloons into a long, partially redundant wall of routing rules (repeated "Do not send those to X" instructions). Most rules are functional given the absence of enums, but the phrasing repeats and could be tightened substantially.

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 no output schema, the description should explain the return; it does so minimally ("answer with an inline widget"). For a five-parameter, mode-driven tool the mode/section matrix is thoroughly covered, though the response format and mode-precedence edge cases are only lightly touched.

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 description coverage is 0%, so the description must carry the full burden, and it does: it defines query, symbols, focus (ai|raw|auto|catalog), source examples, and an extensive section vocabulary with disambiguation rules. This is a case where prose fully compensates for an undocumented schema.

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?

States a specific verb and resource ("Search financial data and return an answer with an inline widget") and enumerates the covered domains (stocks, macro, forex, crypto, commodities, earnings, technicals). It also routes to siblings (list_watchlists/list_portfolios) and distinguishes its Deep Dive modes, so an agent can tell it apart from the rest of the toolset.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: screening a named watchlist requires calling list_watchlists/list_portfolios first, and it spells out the exclusive focus modes (ai/raw/catalog) with their conditions. The negative routing rules (buzz must be section=buzz, not news/catalysts; acceleration not movers; heatmap not sector treemap) are unusually explicit about what NOT to do.

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

All Manawa Terminal toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources