Skip to main content
Glama

get_public_company_financials

Read-only

Use when pulling public company financials for a comparable company analysis, M&A due diligence, or investor brief. Returns SEC EDGAR financial statement data — income statement, balance sheet, and key ratios from filed reports. Note: cache may reflect prior quarter — verify against latest SEC filing for time-sensitive analysis. Example: Salesforce FY2024 — $34.9B revenue, 29% operating margin on services, $4.1B operating cash flow — fundamental anchor for CRM sector comparable analysis. Source: SEC EDGAR synced filings. $0.02 USDC per call.

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": {
      "company_name": "<company_name>"
    },
    "name": "get_public_company_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds genuinely non-obvious context: a stale-cache warning tied to quarterly filing cadence, the upstream data lineage, and a per-call cost of $0.02 USDC. It stops short of describing pagination, coverage limits (e.g. non-US filers, private companies), or failure modes for unknown entities.

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 essential guidance is front-loaded in the first sentence, and the cost and cache caveat are clearly flagged with 'Note:'. The Salesforce example is somewhat over-elaborated with specific revenue, margin, and cash-flow figures, and the trailing 'Source: SEC EDGAR' line partially repeats the opening, though the figures do substitute for a missing output schema.

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, read-only, no-output-schema tool, the description covers return contents, provenance, cost, and freshness risk, which is most of what an agent needs before calling. The remaining material gap is input format and period selection, which is left unresolved across both schema and description.

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 coverage is 0% for the single required parameter, so the description must compensate and largely does not: it never says whether company_name expects a ticker, legal name, or CIK, nor how to disambiguate similarly named companies. The Salesforce FY2024 example hints at entity form but simultaneously reveals there is no period parameter, leaving it unclear which fiscal year a call returns.

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?

The description gives a specific verb and resource ('pulling public company financials'), enumerates the returned artifacts (income statement, balance sheet, key ratios), and names the authoritative source (SEC EDGAR filed reports). That source scope distinguishes it from adjacent siblings such as credit-union financials or market multiples without needing to name them.

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?

It opens with an explicit when-to-use clause covering three named scenarios: comparable company analysis, M&A due diligence, and investor brief. There is no when-not guidance or explicit routing to a sibling for overlapping needs, so it falls 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