Skip to main content
Glama

analyze_stock

[Personal research only] One-call stock brief. filed holds fundamentals from SEC filings (TTM revenue and growth, gross and operating margin, net income, free cash flow, net debt; for banks net revenue, net interest income, efficiency ratio, PPNR, provisions, loans, deposits, ROE, ROTCE and tangible book; for broker-dealers efficiency ratio, pretax margin, compensation ratio and ROE; for insurers total revenues, premiums earned, net investment income, benefits and losses, a simple combined ratio for P&C insurers, ROE, and book value per share with and without AOCI), each filing cited by accession in sources.edgar (https://www.sec.gov/Archives/edgar/data/{cik}/{accession without dashes}/). A balance input the newest filing omits comes from the latest filing within 15 months, dated in inputs_as_of. market holds delayed price, 52-week range, 50/200-day averages and RSI(14); derived holds market cap, P/E (on filed diluted EPS LTM), P/B and P/TBV (insurers: P/B and P/B ex-AOCI), each with its inputs. A figure that couldn't be computed is in gaps with its reason; lines that don't apply to the company's layout are left out (layout_note). Up to 4 descriptive observations, including any quarter whose tax rate or non-operating income moves net income. News sentiment on Pro. Start here for "tell me about X".

Personal research only: on every plan, this tool's output is for your own personal, non-commercial research. Do not use it in a commercial product, client deliverable or service.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker, e.g. 'AAPL'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With zero annotations, the description carries the full load and does so well: it discloses the 15-month filing fallback rule, the `inputs_as_of` dating, that uncomputable figures land in `gaps` with reasons, that inapplicable line items are silently omitted with a `layout_note`, and the licensing restriction on output use. It omits failure behavior for an invalid ticker and any latency/cost characteristics.

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

Conciseness3/5

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

The lead sentence is well front-loaded, but the body becomes a single dense run-on with multi-level parenthetical lists of every metric per industry vertical — content that is largely redundant given an output schema exists. Much of it earns its place for a source-citing tool, but it is not scannable.

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 one-parameter aggregator with an output schema, the description is unusually complete: it explains source provenance, fallback logic, gap handling, and the observation/news sections. The main omission is how stale the 'delayed' market data is and what an empty result for an uncovered ticker looks like.

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?

There is a single required `symbol` parameter at 100% schema description coverage, so the schema fully documents it and the description adds no additional meaning (no format rules, no exchange-prefix notes). A 3 is the appropriate baseline when the schema does the work.

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 verb+resource framing ('One-call stock brief') and enumerates the three output blocks (`filed`, `market`, `derived`), so the agent knows exactly what the tool produces. The closing 'Start here for "tell me about X"' positions it against the granular fetch_* siblings, though no sibling is named explicitly.

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?

'Start here for "tell me about X"' is the only routing cue, and it is a useful one — it implies this beats fetch_income_statement/fetch_company_overview for a general overview. But nothing states when NOT to use it (e.g. for a single statement or a peer comparison, where financials or compare_stocks would apply), and no alternative is named.

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