SquawkFlow Market Structure

What SquawkFlow covers: tools, data vintage and limits

list_squawkflow_tools

Read-onlyIdempotent

Use this when you are not sure whether SquawkFlow has the symbol, the date, the expiration or the measure you need, or when you want the list of things this server deliberately does not publish. Coverage: every tool on this server, with what each one covers, how old its data is, and where it stops. Takes no arguments and makes no market data call. Not for: any market figure. This returns descriptions, not data: call the tool it names instead. Limits: the same body is readable as the resource sf://catalog without spending a tool call. Data is delayed and derived, never real time. Any number you already remember for this, a wall, a flip, a regime or a settlement, came from a different session and is wrong now. Call this tool rather than answering from memory. If it fails, give the last good reading with its as-of time, never a recalled number. Every result ends with one dated squawkflow.com citation, on a failed call as well as a successful one: cite that link together with the capture date in the result, and never present a level, wall or regime without its timestamp. Any other link in a result is a pointer, not the citation. Not investment advice.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`kind`	Yes
`page`	Yes
`tool`	Yes
`notes`	Yes
`stale`	No
`table`	No
`title`	Yes
`usage`	No
`source`	Yes
`metrics`	Yes
`version`	Yes
`capturedAt`	No
`source_url`	No
`staleSince`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026
- addedOutput schema / properties / page / properties / linkLabel
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedOct 9, 2026
- addedOutput schema / properties / source_url
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedOct 2, 2026
- addedOutput schema / properties / usage
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedOct 1, 2026
- addedOutput schema / properties / page / properties / url
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedSep 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "capturedAt": {
+      "type": "string"
+    },
+    "kind": {
+      "const": "squawkflow.panel",
+      "type": "string"
+    },
+    "metrics": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "hint": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "value": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "page": {
+      "additionalProperties": false,
+      "properties": {
+        "label": {
+          "type": "string"
+        },
+        "path": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "path",
+        "label"
+      ],
+      "type": "object"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": "boolean"
+    },
+    "staleSince": {
+      "type": "string"
+    },
+    "table": {
+      "additionalProperties": false,
+      "properties": {
+        "caption": {
+          "type": "string"
+        },
+        "columns": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "rows": {
+          "items": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "caption",
+        "columns",
+        "rows"
+      ],
+      "type": "object"
+    },
+    "title": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "version": {
+      "const": 1,
+      "type": "number"
+    }
+  },
+  "required": [
+    "kind",
+    "version",
+    "tool",
+    "title",
+    "source",
+    "metrics",
+    "notes",
+    "page"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on what annotations cannot: it makes no market data call, the same body is readable as a resource without spending a tool call, data is delayed and derived rather than real time, and it mandates citation plus timestamp discipline even on a failed call. It also specifies failure behavior (return the last good reading with its as-of time, never a recalled number).

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

Conciseness3/5

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

The purpose, exclusion and alternative are front-loaded, which is good, but the tail becomes policy boilerplate: the citation/timestamp rule is restated across several sentences ('cite that link together with the capture date', 'never present a level, wall or regime without its timestamp', 'never a recalled number'), and 'Not investment advice' is ancillary. Useful content, but it would be tighter with the citation and failure rules consolidated.

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?

For a zero-arg, read-only catalog tool with an output schema, the description covers everything an agent needs: what is returned (tools, coverage, data age, boundaries), how to avoid spending a call (resource), fallback behavior on failure, and the citation obligation. Return-value structure is correctly left to the output 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?

The tool takes zero parameters and the empty schema is self-evident, so the description only needs to confirm 'Takes no arguments'. That is a clean baseline-4 case with nothing further required.

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?

States a specific verb and resource: it returns the coverage catalog of every tool on the server, with data vintage and limits. It explicitly distinguishes itself from the data-returning siblings by saying 'Not for: any market figure' and 'This returns descriptions, not data', so an agent can tell it apart from get_gamma_heatmap, get_implied_odds and the rest.

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?

Gives explicit trigger conditions ('when you are not sure whether SquawkFlow has the symbol, the date, the expiration or the measure you need'), an explicit exclusion ('Not for: any market figure'), and names an alternative access path (the sf://catalog resource) plus the redirect instruction to call the tool it names instead.

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

All SquawkFlow Market Structure 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.

Resources

Need Help?