Skip to main content
Glama
screener-mcp
by LogeshR15

get_forward_outlook

Read-only

Combine analyst estimates, order wins, capex/expansion filings, and management guidance into one forward-looking outlook for an Indian stock, avoiding reliance on trailing data.

Instructions

Forward-looking inputs in one call, instead of extrapolating trailing data:

  1. Analyst estimates — current and next fiscal-year EPS and revenue consensus (low/high, growth, analyst count) and forward P/E.

  2. Order wins — NSE filings in the last days announcing orders, contracts, LoAs, with rupee values stated in the headline summed.

  3. Capex & expansion — filings about new capacity, plants, commissioning.

  4. Management guidance — the most relevant passages from the latest earnings call on guidance, order book / pipeline, and capex (needs the [ai] extra; otherwise returns an install hint).

Each part is independent — if one source is down the result is partial.

symbol: NSE/BSE symbol or company name days: filing look-back (30-730, default 180) include_earnings_call: set False to skip the transcript step (faster)

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": {
      "symbol": "<symbol>"
    },
    "name": "get_forward_outlook"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
symbolYes
include_earnings_callNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses real operating behavior: each part is independent, a failed source yields a partial result rather than an error, and the guidance section requires the '[ai]' extra or the tool returns an install hint instead of data. It also notes that rupee values are summed from headline text, which warns the agent about the derivation of that number.

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 numbered breakdown is front-loaded and scannable, with the parameter hints grouped at the end where an agent expects them. A few phrases are padded or awkward — 'with rupee values stated in the headline summed' takes a second read — but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape needn't be spelled out; what matters for a four-source aggregator is degradation behavior and the optional-dependency path, both of which are stated. For a 3-parameter, partial-failure-tolerant tool this leaves no meaningful gap for correct invocation.

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 carries the full burden — and it does: symbol accepts 'NSE/BSE symbol or company name', days is bounded to 30–730 with default 180 and described as a filing look-back, and include_earnings_call is explained in terms of the effect (skips transcript, faster). Every parameter gains meaning the bare schema does not convey.

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 opens with a concrete framing — 'Forward-looking inputs in one call' — and enumerates four specific content blocks (analyst estimates, order wins, capex/expansion, management guidance). That is far more than a restatement of the name. It stops short of naming which sibling it supersedes (e.g. get_analyst_targets overlaps on the EPS/revenue consensus piece), so an agent must infer the boundary itself.

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?

'instead of extrapolating trailing data' gives a clear selection rationale, and 'include_earnings_call: set False to skip the transcript step (faster)' tells the agent when to trade completeness for speed. What is missing is explicit exclusion guidance against the overlapping siblings (get_analyst_targets, get_company_announcements) or a stated condition for choosing those instead.

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