Skip to main content
Glama

Stratalize Intelligence

Get Public Company Financials

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. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the data source (SEC EDGAR synced filings), a genuine staleness caveat ("cache may reflect prior quarter — verify against latest SEC filing"), and a per-call cost of $0.02 USDC. These are behavioral facts an agent cannot get from annotations or schema and that affect whether and how to call it.

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?

It is front-loaded correctly: trigger condition first, then return contents, then the staleness caveat, source, and price. The Salesforce FY2024 illustration is the weakest sentence — useful for output shape but padded with specific figures that do not help an agent decide or call.

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?

For a single-parameter, annotation-covered, read-only fetch with no output schema, the description covers contents (income statement, balance sheet, ratios), provenance, freshness risk, and cost. The remaining gap — which fiscal periods are returned given no period parameter — is only a minor inference.

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?

The single parameter company_name has 0% schema description coverage, and the description never says whether it expects a ticker, legal entity name, or CIK. It also never addresses how a fiscal period is chosen, even though the schema exposes no period parameter. With the schema carrying no meaning, the description fails to compensate for the one ambiguous input.

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?

"Pulling public company financials" plus "Returns SEC EDGAR financial statement data — income statement, balance sheet, and key ratios" gives a specific verb, resource, and output scope. The public-company/SEC-filing framing implicitly separates it from siblings like get_ncua_credit_union_financials or get_bank_financial_intelligence, but 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 Guidelines4/5

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

"Use when pulling public company financials for a comparable company analysis, M&A due diligence, or investor brief" names concrete use contexts an agent can match against a task. It stops short of exclusions or pointing to an alternative (e.g., multiples vs. raw statements), so there is no when-not guidance.

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