Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Operating Metrics (per-company KPIs in the industry-standard set — cruise; SIC-routed)

operating_metrics
Read-onlyIdempotent

A company's operating-KPI time series in the metric set standard for its industry — the structured operating depth a model can't reliably pull from a 10-K itself. You pass a company (ticker/CIK) and get THAT company's values (per-company, not industry aggregates), from MARS's KPI panel extracted from 10-Q / 10-K text.

Covered industries: cruise lines (occupancy, passenger cruise days, APCDs, fuel cost per ton, net cruise costs), P&C insurers (combined / loss / expense ratios, premiums written and earned), homebuilders (net orders, closings, backlog, average selling price, cancellation rate, active communities) and airlines (ASMs, RPMs, load factor, TRASM / PRASM / CASM, yield). The response's industry field says which; each period lists its KPI values and derived_kpis (Q4 values MARS computed as FY minus Q1-Q3). Latest 20 reporting periods by default, newest first. A company with no KPI rows returns status='not_covered'; an unresolvable input returns status='unresolved'.

Input: ticker_or_cik. Heavy verticals (biotech, mining) have their own dedicated tools.

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_or_cik": "<ticker_or_cik>"
    },
    "name": "operating_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_periodsNoLatest N reporting periods (default 20, max 60).
ticker_or_cikYesCompany ticker (Atlas-resolved) or SEC CIK. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, yet the description still adds real behavioral context: default 20 latest periods, newest first, the 10-Q/10-K extraction source, the `derived_kpis` FY-minus-Q1-Q3 computation, and the two failure statuses ('not_covered', 'unresolved'). An agent knows what it gets back and when it gets an empty result.

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?

Front-loaded with the core value proposition and broken into labeled sections (Covered industries, Input) that scan quickly. It is on the longer side and slightly repeats the title's cruise/SIC-routing framing, but nearly every sentence carries selection-relevant information.

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?

There is no output schema, so the description carries the response shape: the `industry` field, per-period KPI values, `derived_kpis`, period count and ordering, and the not_covered/unresolved statuses. For a two-parameter, closed-world read tool, an agent has everything needed to call it and interpret the result.

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?

With 100% schema description coverage the baseline is 3; the description adds that the ticker is 'Atlas-resolved' and that the identifier is a ticker or SEC CIK, plus the newest-first ordering that the schema does not state for `max_periods`. It does not elaborate on the 60-period cap beyond the schema's own text, so it stays close to the minimum.

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 names a specific verb+resource: a company's operating-KPI time series in the metric set standard for its industry, drawn from MARS's 10-Q/10-K-extracted KPI panel. It explicitly distinguishes itself from heavy-vertical tools (biotech, mining) and from industry-aggregate sources by stating 'per-company, not industry aggregates'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

States when to use it (structured operating depth a model can't reliably pull from a 10-K), enumerates exactly which industries are covered, and names the when-not case (heavy verticals have their own dedicated tools). The SIC-routing note in the title and the industry list tell an agent when this tool will actually return data.

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