Skip to main content
Glama

SquawkFlow Market Structure

Search the pages SquawkFlow publishes

search
Read-onlyIdempotent

Use this when you want the SquawkFlow page that answers a question, or a citable link rather than a number: glossary definitions, methodology and explainer pages, expiration calendars, filing pages and dated session records. Returns ids, titles and canonical URLs. Pass an id to fetch to read the page. A query naming an ISO date finds the dated record for it. Coverage: the pages SquawkFlow publishes for machine reading, read from the site's own published index rather than from the API, so a wide reading pass here costs the market data endpoints nothing. Not for: market figures of any kind: this returns pages, not numbers. For a level, a grid, a filing or a record, call the tool that publishes it. Limits: a page the site has not published for machine reading is not findable here, and no id is invented for one. Ranking is a plain lexical match over titles and the published descriptions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults to return, 1 to 20.
queryYesA natural-language query. An ISO date such as 2026-09-17 finds the dated session record for it.

Output Schema

NameRequiredDescriptionDefault
noteYes
queryYes
resultsYes
retrievedAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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/non-destructive/openWorld, but the description adds substantial context they don't cover: coverage is limited to pages published for machine reading, no ids are invented for unpublished pages, and the index is read from the site rather than the API so searches cost the market-data endpoints nothing. It also discloses the ranking mechanism (plain lexical match over titles and published descriptions), which sets expectations about recall.

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?

Front-loaded with the use case, then coverage, exclusions, and limits in a logical order with no filler sentences. It runs long for a two-parameter tool, and the index-vs-API aside is dense, but each sentence carries information an agent would otherwise have to guess.

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?

An output schema exists, so return values need only be sketched, and the description does that (ids, titles, canonical URLs) while explaining the id-to-fetch handoff. Combined with coverage limits, ranking behavior, and the explicit exclusion of market figures, nothing needed to invoke this correctly is missing.

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 baseline is 3, but the description adds meaning beyond the schema: the lexical ranking tells the agent to use title-like keywords rather than semantic phrasing, and the ISO-date behavior is reinforced with the pointer that an id result can be fetched. The limit parameter is left to the schema, which is acceptable given full coverage.

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 — searching the pages SquawkFlow publishes — and enumerates the page classes (glossary, methodology, expiration calendars, filing pages, dated session records). It contrasts itself with number-returning siblings in the first sentence, so an agent can distinguish it from get_gex_levels or get_session_record without opening a 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?

Gives an explicit when-to-use trigger ('when you want the page that answers a question, or a citable link rather than a number') and an explicit exclusion ('Not for: market figures of any kind ... call the tool that publishes it'). The follow-up instruction to pass a returned id to fetch closes the loop on the natural next step.

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