Skip to main content
Glama

SquawkFlow Market Structure

Read one published SquawkFlow page

fetch
Read-onlyIdempotent

Use this when you have an id from search and want the page text itself, with the canonical URL to cite. Returns the published markdown verbatim, so the page carries its own capture stamp and its own limits section into your answer. Coverage: any page with a published markdown mirror. Ids are written page:/path, session:YYYY-MM-DD, glossary:, learn: or institution::, and a squawkflow.com URL is accepted. Not for: arbitrary web pages: only squawkflow.com is served. Current market figures, which are a tool call rather than a page read. Limits: an id that resolves to no published page returns that, and no text is composed in its place. A very long page is truncated with a note naming where it was cut.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id returned by search, for example session:2026-09-17 or page:/learn/how-to-calculate-gamma-exposure. A squawkflow.com URL is accepted.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful behavior: markdown returned verbatim including its own capture stamp and limits section, no text composed when an id resolves to nothing, and truncation with a note naming the cut point. It loses a point because 'only squawkflow.com is served' sits in mild tension with openWorldHint=true, and the return shape beyond 'markdown verbatim' is left to the output schema.

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 predictable order, with no filler sentences. The sentence about the page carrying 'its own capture stamp and its own limits section into your answer' is slightly wordy for the point it makes, but every part is load-bearing.

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 single-parameter read tool with a full output schema, the description covers what it returns, which ids are valid, what happens on a miss, and what happens on oversized input. Nothing an agent needs in order to call it correctly or interpret a miss 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% and the schema already gives two id examples, so the baseline would be 3. The description goes beyond it by enumerating the full id grammar (page:/path, session:YYYY-MM-DD, glossary:<slug>, learn:<slug>, institution:<slug>:<YYYY-qN>) and confirming a squawkflow.com URL is accepted, which is real added meaning for constructing a valid call.

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 ('Read one published SquawkFlow page', 'the page text itself, with the canonical URL to cite') and immediately distinguishes itself from search by tying the input to 'an id from search'. An agent knows exactly what it gets back without opening the 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 ('you have an id from search and want the page text itself') and two explicit not-for cases: arbitrary web pages, and current market figures which are 'a tool call rather than a page read'. The alternative for market data is named by category rather than by tool name, but the exclusion is unambiguous.

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