Skip to main content
Glama

SquawkFlow Market Structure

SquawkFlow session record: what was published before a session

get_session_record
Read-onlyIdempotent

Use this when the question is what SquawkFlow published for a given trading day before it traded, and what the record says happened to those levels. Returns the dated record for one session: the levels as published, the verdict on each one, the capture coverage, how the published levels moved from the prior session, and whether the record has settled or is still open. This is the dated tool on this server: pass a date to ask about a past session. Coverage: one SPX session per call, for the dates the published index lists. The index is the whole coverage: a date it does not list has no record here. Not for: the current reading (get_gex_levels); any rate, share or frequency computed across sessions, which this server does not compute; any forward statement about a session that has not happened. Limits: one session per call. No session price extremes are published through this tool: the open, close, high and low on the record are vendor-derived and are not relayed, nor is any comparison computed from them. A weekend or a holiday returns that it was not a session, which is a different answer from a missing record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_session_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO session date. Omit for the most recent published record. A date the published index does not list returns that answer rather than an error.

Output Schema

NameRequiredDescriptionDefault
kindYes
pageYes
toolYes
notesYes
staleNo
tableNo
titleYes
usageNo
sourceYes
metricsYes
versionYes
capturedAtNo
source_urlNo
staleSinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / linkLabel
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / source_url
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / usage
      Added value: +{
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / page / properties / url
      Added value: +{
      +  "type": "string"
      +}
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and open-world behavior, and the description goes well beyond them: one-session-per-call limit, the published index as the entire coverage boundary, a weekend/holiday returning 'not a session' versus a missing record, and the explicit note that vendor-derived open/close/high/low are not relayed. That last point is materially useful behavior disclosure since a 'session record' would otherwise imply price extremes.

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 definition is front-loaded with the use case and then sequenced into coverage, exclusions, limits, and edge cases, which reads well. It loses a little to repetition — 'one session per call' appears twice under Coverage and Limits, and the unlisted-date rule restates the schema's own note.

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?

A single optional parameter, full annotations, and an output schema mean the description only needs to carry routing and edge-case behavior — which it does. Coverage boundaries, the weekend/holiday distinction, and the withheld vendor-derived extremes are exactly the gaps an agent would otherwise hit on first call.

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 the date format, omission default, and unlisted-date behavior are already documented. The description nonetheless adds a real semantic layer by explaining the index as the coverage boundary for dates, which reframes what a passed date resolves to. The gain is modest but genuine, so slightly above baseline.

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 and resource — returns the dated record for one session — and enumerates its contents: published levels, per-level verdict, capture coverage, movement from the prior session, and settled/open state. It explicitly contrasts the current reading with get_gex_levels, so the agent can separate it from siblings without opening either schema.

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?

It gives an explicit when: 'Use this when the question is what SquawkFlow published for a given trading day before it traded.' It then names three exclusions with reasons — current reading (get_gex_levels), cross-session computed rates/shares/frequencies, and forward statements — leaving very little to inference.

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