Skip to main content
Glama
Sign In
flowscan-mcp

flowscan-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Weekend trading: Friday close vs current/Monday prices

flowscan_weekend_prices
Read-only

Fetches Friday-close, Sunday-close, or live weekend prices and weekend percentage/dollar changes for HIP-3 TradFi perpetual markets like xyz:TSLA and xyz:GOLD.

Instructions

Weekend page price table: for HIP-3 TradFi perps (e.g. 'xyz:TSLA', 'xyz:GOLD'; stocks, indices, commodities, FX), the Friday-close prices, Sunday-close prices (once the weekend is over), live current prices (during an active weekend), and weekendChanges {pct, dollar} per market, plus status and price counts.

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": "flowscan_weekend_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNofridayCloseTs (ms) or a YYYY-MM-DD date in that weekend. Default: latest.
fieldsNoPaths to keep, relative to `data` (list tools: each row); misses go to _fieldsNotFound.
marketNoFilter by market symbol substring, e.g. 'TSLA' or 'xyz:'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carrying the stateful behavior adds real value: which price columns exist depends on whether a weekend is active or finished. It also discloses the weekendChanges {pct, dollar} shape and the presence of status/price counts, which the annotations do not cover.

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?

A single dense sentence, but it front-loads the resource and then enumerates fields, so a reader gets the core identity immediately. No filler or repetition; the long parenthetical list is the only cost to readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates the returned rows and fields, and annotations already cover the read-only/open-world safety profile. Given only three well-documented optional params, an agent has enough to call it correctly; the missing piece is guidance on when to choose it over siblings.

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?

Schema description coverage is 100%, so the week/fields/market semantics are already documented (fridayCloseTs or YYYY-MM-DD, path filtering with _fieldsNotFound, substring market match). The description adds no further parameter guidance beyond schema baseline, so 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource precisely ('Weekend page price table' for HIP-3 TradFi perps) and enumerates the specific data columns returned: Friday-close, Sunday-close, live current, weekendChanges, status, counts. It is clearly distinguishable from flowscan_weekend_weeks or flowscan_weekend_positions, though the opening phrase 'Weekend page price table' is slightly jargon-y rather than a clean verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use statement, no prerequisite, and no alternative named. The temporal conditions ('once the weekend is over', 'during an active weekend') describe data availability rather than telling an agent when to pick this tool over sibling weekend tools.

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

Deploy Server

Other Tools