Skip to main content
Glama
screener-mcp
by LogeshR15

analyze_red_flags

Read-only

Detects financial red flags across a company's full history, including falling promoter holding, rising leverage, weak cash flow, and equity dilution, with severity, thresholds, and supporting numbers.

Instructions

Rule-based red-flag checks over a company's full history — computed here, each flag with its severity and the numbers behind it:

  • Promoter holding falling, promoter shares pledged

  • Leverage (debt-to-equity) and borrowings outgrowing sales

  • ROCE falling or below 10%

  • Operating cash flow lagging net profit (and negative CFO)

  • Sales growing much faster than profit

  • Debtor / inventory days rising

  • Profit leaning on other income (one-offs)

  • Equity dilution

Returns flags (sorted by severity), clean_checks, skipped_checks (e.g. leverage for banks, promoter checks for a company with no promoter), the thresholds used, and not_checked items that need the annual report.

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

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

A3.5/5.0
Behavior4/5

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

Annotations only say readOnly and openWorld. The description adds genuinely useful behavior: checks are computed here from full history, flags are severity-sorted, and some checks are legitimately skipped (leverage for banks, promoter checks when no promoter exists) with thresholds and not_checked items surfaced. It stops short of saying anything about data freshness or cost of the call.

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 one-line purpose, then a scannable bullet list of checks and a returns paragraph. The dangling 'symbol: NSE/BSE symbol' line at the end sits awkwardly after the return description rather than with the inputs.

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?

Even though an output schema exists, the description adds orientation about severity ordering, clean vs skipped vs not_checked categories, which materially helps interpret results. The missing piece is the financial_type parameter and any hint about the data source or staleness.

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 coverage is 0%, so the description must carry the parameter burden. It clarifies the symbol format ('NSE/BSE symbol'), which is real added value, but the second parameter financial_type (default 'consolidated') is never mentioned, leaving the agent to guess between standalone and consolidated.

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?

Names a specific verb ('rule-based red-flag checks') and resource ('a company's full history') and enumerates the exact check families, so the agent knows precisely what it gets. It never names or contrasts with a sibling such as get_full_analysis or get_moat_signals, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the check list that this is a risk-screening tool, and cannot tell from the text whether it should call this or get_full_analysis first.

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