Skip to main content
Glama
Sign In

Ava Advisor

by fund.ava
OverviewDiscussionsAdmin

Private Movers

private_movers
Read-only

Off-coverage / private companies the news moved within a theme — the 'beyond tickers' surface. limit = how many (default 20, max 50). Returns {companies, count, total, note?} — honor note when total > count (it's a top slice, not the whole set).

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": {
      "theme": "<theme>"
    },
    "name": "private_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 20, hard cap 50). Keep SMALL + narrow the scope; page/refine rather than dump — heavily-covered assets have hundreds of articles.
themeYesA megatrend theme — name/slug (resolved for you) or node id.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely new behavior: the return shape and the instruction to honor `note` when `total` exceeds `count` because results are a top slice. It stops short of saying how the slice is ranked or whether coverage is per-company or per-article scope.

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?

Three short, front-loaded fragments with zero filler; the purpose leads, then the parameter note, then the return contract. Slight redundancy by repeating the limit default and cap that the schema already documents.

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?

Since there is no output schema, describing {companies, count, total, note?} and the truncation caveat is valuable and largely completes the return story. However, for a three-parameter tool with a required `theme`, the description leaves ranking logic and the relationship to theme_players unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including detailed guidance for `country` and the limit cap, so the baseline is 3. The description's `limit` default/max largely restates the schema and it adds nothing about `theme` or `country` semantics.

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?

Description states a specific verb and resource: private/off-coverage companies whose news moved within a theme, framed as the 'beyond tickers' surface. That phrasing implicitly distinguishes it from the public-ticker sibling theme_players, though the sibling is never named.

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 only implied through 'off-coverage' and 'beyond tickers' — an agent can infer this is for non-listed names, but there is no explicit when-to-use/when-not or named alternative such as theme_players or stock_impact.

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