Skip to main content
Glama
screener-mcp
by LogeshR15

get_full_analysis

Read-only

Fetch all financial data for a company in one report, including statements, ratios, quarterly results, shareholding, and peer comparisons, to support thorough or beginner-friendly analysis.

Instructions

Fetch ALL financial data for a company in a single call, as one report.

Uses the same windows as the standalone tools, so numbers always agree:

  • Key ratios, about, NSE/BSE codes

  • 10 fiscal years of P&L (+ TTM), Balance Sheet, Cash Flow

  • Ratios history incl. ROE, debt-to-equity, year-end P/E and P/B

  • 8 quarters of results

  • 8 quarters of shareholding

  • Peer comparison table

Use this for a thorough analysis, to explain a company (including to a beginner), or to answer complex multi-part questions.

symbol: NSE/BSE symbol

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_full_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
financial_typeNoconsolidated

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the valuable non-obvious trait that this returns a very large payload (10 years, 8 quarters, peer table) in one call. It does not mention response size limits, latency, or auth requirements, which keeps it short of 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?

Front-loaded with the core action, then a scannable bulleted inventory of included data, then usage guidance and the one parameter note. The bullet list is long but each line corresponds to real returned content; only the trailing symbol note is redundant with the schema title.

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 large aggregate tool the description covers scope, data recency windows, and intended use, and an output schema exists so return structure need not be explained. The missing piece is the financial_type parameter, the one omission that could cause an incorrect call.

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

Parameters2/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 meaning. It only explains symbol as an "NSE/BSE symbol"; financial_type is never mentioned, leaving the agent unaware that consolidated vs standalone exists and silently defaults to consolidated — a choice that materially changes the numbers.

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 ("Fetch ALL financial data for a company in a single call, as one report") and enumerates exactly which blocks are included (10 fiscal years P&L, 8 quarters, peers). It distinguishes itself from the standalone tools by noting it uses the same windows, so an agent can tell it is the aggregate one-shot variant.

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?

Gives clear positive contexts: thorough analysis, explaining a company to a beginner, complex multi-part questions. The reference to the standalone tools implies an alternative for narrower needs, but there is no explicit "do not use this for a single metric" exclusion or a named sibling to route to.

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