Skip to main content
Glama

ko-mcp

by io.github.SharpLu
OverviewDiscussionsAdmin

get_ftd_data

Read-onlyIdempotent

Get SEC fails-to-deliver (FTD) data for a stock. Each quantity is the aggregate net BALANCE of shares that had failed to deliver and were still outstanding on that settlement date, as published by the SEC -- NOT the number of new fails that day. Balances carry over between days, so never sum quantities across dates (that counts the same unsettled shares repeatedly); compare levels or take the maximum instead. Fails arise from many causes (operational and processing delays, long sales, market-maker activity), and FTD data on its own is not evidence of naked short selling. Free/keyless access covers the trailing 92 days. structuredContent carries the exact share quantities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoDays of settlement-date history (default 90; Free/keyless access allows up to 92)
pageNoPage number (default 1)
limitNoRows 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.
tickerYesStock ticker symbol (e.g. 'GME', 'TSLA')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYes
pagingYesPaging state reconciled from ko.io meta.total_count and meta.softwall
tickerYes
measureYesEach quantity is the balance of fails outstanding on that settlement date -- not new fails that day; never sum across dates
plan_limitYesThe Free/keyless plan limits ko.io applied to this answer (null for paid callers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Number of days of history (default 90)"New value: +"Days of settlement-date history (default 90; Free/keyless access allows up to 92)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "measure": {
+      "const": "outstanding_fail_balance",
+      "description": "Each quantity is the balance of fails outstanding on that settlement date -- not new fails that day; never sum across dates",
+      "type": "string"
+    },
+    "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"
+    },
+    "plan_limit": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "continuation": {
+              "$ref": "#/properties/rows/items/properties/settlement_date"
+            },
+            "date_basis": {
+              "$ref": "#/properties/rows/items/properties/settlement_date"
+            },
+            "effective_period": {
+              "$ref": "#/properties/rows/items/properties/settlement_date"
+            },
+            "policy_version": {
+              "$ref": "#/properties/rows/items/properties/settlement_date"
+            },
+            "row_cap": {
+              "anyOf": [
+                {
+                  "$ref": "#/properties/paging/properties/total_count/anyOf/0"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "truncated": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "window_end": {
+              "$ref": "#/properties/rows/items/properties/settlement_date"
+            },
+            "window_start": {
+              "$ref": "#/properties/rows/items/properties/settlement_date"
+            }
+          },
+          "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)"
+    },
+    "rows": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "price": {
+            "anyOf": [
+              {
+                "$ref": "#/properties/rows/items/properties/quantity/anyOf/0"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Exact decimal string as served by ko.io (not rounded); null = unknown"
+          },
+          "quantity": {
+            "anyOf": [
+              {
+                "pattern": "^-?\\d+(\\.\\d+)?([eE][-+]?\\d+)?$",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Outstanding fails-to-deliver balance (shares) on that settlement date"
+          },
+          "settlement_date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ticker": {
+            "$ref": "#/properties/rows/items/properties/settlement_date"
+          }
+        },
+        "required": [
+          "settlement_date",
+          "ticker",
+          "quantity",
+          "price"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ticker": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ticker",
+    "measure",
+    "rows",
+    "paging",
+    "plan_limit"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • 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"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds substantial behavioral context beyond annotations: quantities are aggregate net balances (not new fails), balances carry over between days, free/keyless access covers 92 days, and the data should not be interpreted as evidence of naked short selling. This goes far beyond what annotations provide.

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 efficiently structured, leading with the purpose, then clarifying the data semantics, warning about summation, noting access limits, and adding interpretation caveats. Each sentence adds value without redundancy, and the critical warnings are front-loaded.

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?

The description covers all essential context: data meaning, the summation pitfall, access limits, and interpretation caveats. Combined with the schema's parameter descriptions and the output schema, an agent has everything needed to call the tool correctly and interpret results without ambiguity.

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

Parameters3/5

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

All four parameters are fully described in the schema (100% coverage), so the description adds little additional parameter-level detail. It does reiterate the free-access limit for days, but that is already in the schema. The description's main value is in interpreting the data, not the parameters themselves.

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 clearly states the tool retrieves SEC fails-to-deliver (FTD) data for a stock, specifying the verb, resource, and scope. It distinguishes this from other stock data tools by emphasizing that quantities are aggregate net balances, not new fails, which is a unique and precise purpose.

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?

The description provides explicit usage guidance: never sum quantities across dates because they are balances that carry over, and it warns that FTD data alone is not evidence of naked short selling. It does not explicitly name alternative tools, but the unique data type makes the usage context clear, and the guidance prevents common misuse.

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

All ko-mcp toolsInspect
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.

Resources