ko-mcp

get_financial_stress

Read-onlyIdempotent

Get the OFR Financial Stress Index — a daily indicator of stress in global financial markets. Values above 0 indicate above-average stress.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Number of days of history (default 365)
`page`	No	Page number (default 1)
`limit`	No	Rows per page, 1-500 (default 100). A long `days` window can hold more rows than one page; the answer says when the page is full and names the next one.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	Yes
`paging`	Yes	Paging state reconciled from ko.io meta.total_count and meta.softwall

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": {
+    "paging": {
+      "additionalProperties": false,
+      "description": "Paging state reconciled from ko.io meta.total_count and meta.softwall",
+      "properties": {
+        "continuation": {
+          "description": "SIGNIN_REQUIRED = page>1 needs a (free) ko.io API key",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "has_more": {
+          "description": "null = a full page came back and more MAY exist",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "next_page": {
+          "anyOf": [
+            {
+              "$ref": "#/properties/paging/properties/total_count/anyOf/0"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Next page THIS caller can open; null when there is none (or sign-in is required)"
+        },
+        "page": {
+          "type": "integer"
+        },
+        "per_page": {
+          "type": "integer"
+        },
+        "plan_row_cap": {
+          "anyOf": [
+            {
+              "$ref": "#/properties/paging/properties/total_count/anyOf/0"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Row cap the caller's plan applied to this page, if any"
+        },
+        "returned": {
+          "type": "integer"
+        },
+        "total_count": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Total rows matching the request, when ko.io reported it"
+        },
+        "truncated_by_plan": {
+          "description": "True when the plan's row cap withheld rows from this page",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "page",
+        "per_page",
+        "returned",
+        "total_count",
+        "has_more",
+        "next_page",
+        "continuation",
+        "plan_row_cap",
+        "truncated_by_plan"
+      ],
+      "type": "object"
+    },
+    "rows": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "series": {
+            "$ref": "#/properties/rows/items/properties/date"
+          },
+          "value": {
+            "anyOf": [
+              {
+                "pattern": "^-?\\d+(\\.\\d+)?([eE][-+]?\\d+)?$",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Exact decimal string as served by ko.io (not rounded); null = unknown"
+          }
+        },
+        "required": [
+          "date",
+          "series",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "rows",
+    "paging"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 12, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 100,
+  "description": "Rows per page, 1-500 (default 100). A long `days` window can hold more rows than one page; the answer says when the page is full and names the next one.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / page

Added value: +{
+  "default": 1,
+  "description": "Page number (default 1)",
+  "minimum": 1,
+  "type": "integer"
+}

First observedJul 11, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the interpretive context that values above 0 indicate above-average stress, which is useful. However, it does not mention pagination or the fact that long time windows may page, which is only hinted in the parameter description.

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 description is two sentences, efficient and front-loaded with the core purpose, followed by a brief interpretation. No wasted words, though it could be slightly longer to cover usage guidelines without becoming bloated.

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?

The tool is simple with 0 required params, an output schema, and full schema description coverage, so it does not need extensive description. However, it lacks guidance on pagination for long time windows and does not explain what fields the output contains (though output schema covers that). It is mostly complete but could improve by mentioning pagination behavior explicitly.

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 schema description coverage is 100%, with each parameter having a clear description. The description itself adds a small interpretive note about stress values, but the parameter descriptions already cover what each parameter does. The description does not need to duplicate schema content; the schema is sufficient, so a baseline of 3 applies, but the description's mention of 'global financial markets' adds minor context, justifying a 4.

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 clearly states that the tool retrieves the OFR Financial Stress Index, a specific resource with a clear domain (financial markets stress). The verb 'get' and the named index distinguish it from siblings like get_economic_indicators, though it does not explicitly mention which sibling to use for broader economic data.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool compared to alternatives like get_economic_indicators or get_stock_financials. The description implies it is for financial stress monitoring, but does not state when not to use it or mention any competing tools that might also provide similar indicator data.

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.