Skip to main content
Glama
Sign In

Ava Advisor

by fund.ava
OverviewDiscussionsAdmin

Brief

brief
Read-only

The generalized ANALYST BRIEF — one composed "how is doing right now?" picture (pulse + net direction, top_stories, winners/losers, aspect_heatmap, top_entities, top_assets) for any AND-combination of scopes. ⭐ Use to SUMMARIZE a scope (theme / news category / country / sector / aspect) — NOT a raw article list (that's search_news/news_feed). ⛔ NOT for a single COMPANY or market INDEX ("how is AAPL / the S&P doing?" → options_sentiment + stock_impact/news_feed; an index maps to an ETF, not a brief scope). For a sector×region the quickest path is pulse(kind='theme', target='banks', country=…); use brief for one precise GICS cohort or an AND-combo. Scope by ≥1 of (CSV for several) — REQUIRED (never whole-market): • news_type — a category; use ONLY these EXACT names: product_tech, ma_partnership, industry_thematic, earnings_results, corporate_action, management_governance, analyst_rating, macro_economic, geopolitics, commodity_supply, regulatory_legal, cybersecurity_digital_trust, digital_finance_tokenization, price_action_technical, crypto_related, forex_related, analyst_forecast. (commodity→commodity_supply; central-bank/rates→macro_economic — there is NO 'monetary_policy'.) • country (ISO-2) · aspect (impact channel) · gics (code or plain English) · megatrend (theme name/id). ⚠️ News coverage starts 2026-01-01. node+ripple appear only when a SINGLE megatrend anchors the brief.

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": "brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoUpper time bound, ISO date `YYYY-MM-DD`.
gicsNoA GICS sector/industry — a CODE PREFIX (sector `25` / group `2550` / industry `255010` / sub `25501010`, CSV for several) OR plain English ('banks', 'semiconductors', 'biotech'); the server resolves it. 🔴 ENGLISH (translate the concept first: ธนาคาร→'banks'). So 'European banks' = gics='banks' + country=EU codes.
langNoTranslate title/brief_text: `en`|`th`|`ja`.
from_NoLower time bound, ISO date `YYYY-MM-DD`. ⚠️ Ava Advisor NEWS coverage starts 2026-01-01 (nothing before).
aspectNoImpact CHANNEL filter (e.g. `demand`, `competition`, `tariff`, `monetary`). Omit → all channels.
windowNoNews-recency window: `7d`/`30d`/`90d`/`180d`/`1y` or `mtd`/`qtd`/`ytd`. Omit → a sensible default. (Price history is unaffected — this only scopes the NEWS lens.)30d
countryNoMarket filter — CSV of ISO-2 codes (e.g. `US` or `CN,TW,HK`). 🌍 If the question names a NATIONALITY or REGION ('European','Thai','Chinese','ASEAN'), put it HERE — never leave it inside a concept/`q`/`gics` field. Enumerate a region into its member ISO-2s yourself (Europe→GB,DE,FR,IT,ES,NL,CH,SE; ASEAN→TH,SG,MY,ID,PH,VN).
intervalNoTime-bucketing of the pulse series: `day`|`week`|`month`.
megatrendNoA megatrend node — a name/slug (resolved for you, e.g. `foundry`) or an int node id. CSV for several.
news_typeNoNews CATEGORY (exact names only, e.g. `macro_economic`, `commodity_supply`, `earnings_results`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the behavioral burden and does add real context: news coverage begins 2026-01-01, and node/ripple fields appear only when a single megatrend anchors the brief. It does not cover latency, result caps, or fallback behavior when a scope resolves to nothing, which keeps it off a 5.

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?

The core routing rule is front-loaded in the first two sentences and the parameter notes are cleanly bulleted, so structure is good. It is nonetheless long and heavily decorated with emoji and bold markers, which adds visual noise an agent must parse around.

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-parameter, no-output-schema tool, the description covers scope selection, naming rules, regional handling, and coverage limits well. The one inconsistency is that it declares scoping 'REQUIRED (never whole-market)' while the schema lists zero required parameters, leaving the agent unsure whether an unscoped call will error or return a whole-market brief.

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?

With 100% schema coverage the baseline is 3, but the description goes well beyond it: it enumerates the exact permitted news_type values (compensating for the schema's missing enum), maps ambiguous concepts (commodity→commodity_supply, central-bank→macro_economic, no 'monetary_policy'), and instructs that nationality/region belongs in `country` with manual ISO-2 enumeration. That is genuine guidance the schema does not supply.

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?

The description names a specific composite artifact and enumerates its constituent parts (pulse, net direction, top_stories, winners/losers, aspect_heatmap, top_entities, top_assets), so an agent knows exactly what comes back. It explicitly distinguishes itself from search_news/news_feed (raw articles) and from options_sentiment/stock_impact (single company or index), making sibling selection unambiguous.

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?

It gives explicit use/do-not-use rules: use to SUMMARIZE a theme/category/country/sector/aspect, not for a raw article list, and not for a single company or index (with the correct alternatives named for each). It also routes a specific sub-case — sector×region — to pulse(kind='theme', ...) and reserves brief for a precise GICS cohort or AND-combo.

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

All Ava Advisor 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