Skip to main content
Glama

BRAINIAC Company Intelligence

Get company financials

company-intelligence_financials

Retrieve and normalize financial metrics from SEC EDGAR using CIK or ticker. Price $0.05 USDC. POST /api/v1/company-intelligence/financials. Unpaid calls return 402 and do not run.

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": {
      "identifier": "<identifier>"
    },
    "name": "company-intelligence_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior beyond the schema: a per-call price of $0.05 USDC, the failure mode that unpaid calls return HTTP 402 and do not execute, and the underlying POST endpoint. It stops short of stating rate limits, caching, or data freshness, so it is not exhaustive.

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?

Four short sentences, front-loaded with the core purpose, followed by pricing, endpoint, and failure behavior. Nothing is padded, though the raw endpoint path is of marginal value to an agent compared with more detail on the returned metrics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description says only that metrics are 'normalized' without indicating which metrics, what period, or the response shape. Pricing and the 402 behavior are well covered, but an agent cannot anticipate the payload it will receive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'identifier' parameter has 0% schema description coverage, so the description must compensate, and it does by clarifying that the value may be a CIK or a ticker. It does not specify accepted formats or validation rules beyond that, leaving some ambiguity about how each form is recognized.

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 gives a specific verb ('Retrieve and normalize'), a specific resource ('financial metrics'), and the source ('SEC EDGAR'). The resource name 'financials' naturally separates it from sibling resources like filings, ownership, and profile, though it never explicitly contrasts itself with them.

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?

Usage is implied: call this when you need standardized financial metrics for a company identified by CIK or ticker. There is no explicit statement of when to prefer this over siblings such as filings, and no exclusions or prerequisites beyond the payment condition.

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