Skip to main content
Glama

StockPortfolio.pro

Red flags

get_red_flags
Read-only

Conservative warning signs computed from a company’s filed statements — receivables or inventory outrunning sales, earnings ahead of cash, dilution, heavy debt, shrinking margins — each with the filed figures behind it. A missing figure never raises a flag, and nothing here is a judgement or advice. Costs one data lookup.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_red_flags"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesUS ticker, e.g. NVDA or AAPL.

Output Schema

NameRequiredDescriptionDefault
asOfNo
flagsNo
sourceNo
symbolNo
flagCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuine operational context on top: null handling ('a missing figure never raises a flag'), conservative methodology, the fact each flag carries its supporting filed figures, and a cost signal. The one gap is that it never says what a clean result looks like (empty list vs. a 'no flags' object), which matters for an agent parsing the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then the concrete signal list, then the two caveats that actually change agent behavior (missing figures, not advice) and the cost note. No filler sentences and nothing repeated from the schema or annotations.

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?

Single required parameter, full schema coverage, output schema present, and closed-world/read-only annotations — the description fills the remaining gaps (methodology, null semantics, per-flag evidence, cost, non-advice disclaimer). Nothing an agent needs to select or invoke this correctly is missing.

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?

Only one parameter (ticker), and the schema already documents it at 100% coverage with a concrete example format (NVDA, AAPL). The description adds no formatting, exchange, or ambiguity guidance beyond the schema, so baseline 3 applies.

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?

Names a specific computation (warning signs / red flags) over a specific resource (a company's filed statements), and enumerates the concrete signals — receivables or inventory outrunning sales, earnings ahead of cash, dilution, heavy debt, shrinking margins — so an agent knows exactly what output to expect. That enumeration also separates it from generic siblings like get_company_fundamentals and sp_health.

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?

Establishes clear context: use it to surface conservative accounting/financial warning signs, and explicitly bounds the output as non-judgemental and non-advice. It also notes the cost ('one data lookup'), which helps an agent decide whether to call it early. It never names an alternative (e.g. sp_health vs. this) or states when NOT to call it, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources