ko-mcp

get_stock_financials

Read-onlyIdempotent

Get quarterly or annual financial statements for a company (revenue, net income, EPS, margins, cash flow, debt ratios) from SEC 10-K/10-Q filings. Plan limits: the Free plan and keyless access return only the latest quarterly statement; annual statements and earlier quarters require Pro (a request for them returns an explicit plan-limit error, never 'no data'). structuredContent carries the exact reported values.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of periods to return (default 8)
`ticker`	Yes	Stock ticker symbol (e.g. 'AAPL', 'MSFT')
`period_type`	No	Period type — quarterly (10-Q) or annual (10-K)	quarterly

Output Schema

TableJSON Schema

Name	Required	Description
`ticker`	Yes
`periods`	Yes
`plan_note`	Yes	Set when the caller's plan limited which periods were returned
`plan_limit`	Yes	The Free/keyless plan limits ko.io applied to this answer (null for paid callers)
`period_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "period_type": {
+      "enum": [
+        "quarterly",
+        "annual"
+      ],
+      "type": "string"
+    },
+    "periods": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "eps_basic": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          },
+          "eps_diluted": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          },
+          "gross_profit": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          },
+          "long_term_debt": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          },
+          "net_income": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          },
+          "operating_cashflow": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          },
+          "operating_income": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          },
+          "period_end": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "revenue": {
+            "anyOf": [
+              {
+                "pattern": "^-?\\d+(\\.\\d+)?([eE][-+]?\\d+)?$",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Exact decimal string as served by ko.io (not rounded); null = unknown"
+          },
+          "short_term_debt": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          },
+          "stockholders_equity": {
+            "$ref": "#/properties/periods/items/properties/revenue"
+          }
+        },
+        "required": [
+          "period_end",
+          "revenue",
+          "net_income",
+          "eps_basic",
+          "eps_diluted",
+          "gross_profit",
+          "operating_income",
+          "operating_cashflow",
+          "long_term_debt",
+          "short_term_debt",
+          "stockholders_equity"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "plan_limit": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "continuation": {
+              "$ref": "#/properties/periods/items/properties/period_end"
+            },
+            "date_basis": {
+              "$ref": "#/properties/periods/items/properties/period_end"
+            },
+            "effective_period": {
+              "$ref": "#/properties/periods/items/properties/period_end"
+            },
+            "policy_version": {
+              "$ref": "#/properties/periods/items/properties/period_end"
+            },
+            "row_cap": {
+              "anyOf": [
+                {
+                  "type": "integer"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "truncated": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "window_end": {
+              "$ref": "#/properties/periods/items/properties/period_end"
+            },
+            "window_start": {
+              "$ref": "#/properties/periods/items/properties/period_end"
+            }
+          },
+          "required": [
+            "policy_version",
+            "window_start",
+            "window_end",
+            "effective_period",
+            "date_basis",
+            "row_cap",
+            "truncated",
+            "continuation"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The Free/keyless plan limits ko.io applied to this answer (null for paid callers)"
+    },
+    "plan_note": {
+      "description": "Set when the caller's plan limited which periods were returned",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ticker": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ticker",
+    "period_type",
+    "periods",
+    "plan_note",
+    "plan_limit"
+  ],
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description goes beyond these by disclosing the plan-based limitation (Free/keyless returns only the latest quarterly statement), the exact error type (plan-limit error vs 'no data'), and the fact that structuredContent carries exact reported values. This adds meaningful behavioral detail not captured in annotations.

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

Conciseness5/5

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

The description is two sentences with zero filler. The first sentence states purpose and scope; the second delivers plan limits and a note on the structuredContent output. It is front-loaded with the core function, and every clause earns its place. This is exemplary conciseness.

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?

The tool has only 3 parameters, no nested objects, and an output schema exists (structuredContent). The description covers the key operational constraints (plan limits, error semantics) and confirms the return payload (structuredContent). It doesn't explicitly describe the response shape or pagination, but given the output schema exists, that is not required. It is complete enough for an agent to call it correctly, though a brief note on the default limit of 8 periods could be inferred from the schema.

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?

Schema coverage is 100%, so parameters are already documented (ticker, limit, period_type). The description adds value by clarifying that the limit parameter may be constrained by plan (Free plan returns only the latest quarterly, so higher limits on free tier likely trigger an error) and that period_type 'annual' also requires Pro. This goes beyond the schema's basic descriptions, providing operational context for how parameters interact with plan limits.

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 opens with a specific verb ('Get') and resource ('quarterly or annual financial statements'), lists the concrete metrics (revenue, net income, EPS, margins, cash flow, debt ratios), and names the source (SEC 10-K/10-Q). This clearly distinguishes it from siblings like get_stock_price (price) and get_stock_activity (trading activity), so an agent can select it without ambiguity.

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?

The description gives important usage context via plan limits (Free/keyless returns only latest quarterly; annual and earlier quarters require Pro) and specifies error behavior (explicit plan-limit error, never 'no data'). However, it does not explicitly state when to choose this tool over alternatives, nor does it mention any exclusion criteria. The plan-limit guidance is useful for when the tool can be used, but there's no direct contrast with sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ko-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.