Skip to main content
Glama

f1ow

by com.f1ow

Market Quotes

market_quotes
Read-only

Per-coin market snapshot (spot price, perpetual mark price, 24h change, funding rate, open interest, long/short ratio, 24h liquidations), merged across providers. Spot and perp prices are separate fields (spot from spot-market providers, perp mark from the perp venue); they differ by the basis. Pass 'symbols' to filter to specific coins; omit it for every covered coin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolsNoCoin symbols to include, e.g. ["BTC","ETH"]. Omit for all covered coins.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
quotesNo

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description explains that prices come from different sources, that spot and perp fields are intentionally separate, and that the difference is the basis. This prevents an agent from misreading the combined snapshot as a single unified price.

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

Conciseness5/5

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

Three sentences, each carrying distinct information: scope/fields, price-source semantics, and filtering. There is no filler or duplicated annotation content.

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?

With an output schema present and readOnlyHint set, the description covers the tool's purpose, data semantics, provider merge behavior, and parameter usage. No critical calling context is missing.

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?

The schema already fully documents 'symbols' with an example and omit behavior at 100% coverage. The description restates that but adds no new semantic detail beyond 'covered coin'.

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 opens with a concrete noun phrase ('Per-coin market snapshot') and enumerates specific data fields, making the tool's scope clear. The per-coin scope and merged-provider wording differentiate it from market_overview and funding_current, even without naming them.

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

Usage Guidelines3/5

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

The symbol parameter usage is explicit ('Pass symbols to filter... omit for every covered coin'), but there is no guidance about when to prefer this tool over funding_current, derivatives_open_interest, or market_candles. Usage context is implied by the snapshot wording rather than explicit.

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

All f1ow toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Tools are grouped by clear prefixes and mostly target distinct resources; market_quotes vs research_token_view, market_top_movers vs market_trending, and funding_current vs market_quotes have some field or purpose overlap, but descriptions draw enough scope boundaries for an agent to choose correctly in most cases. No two tools are truly interchangeable.

Naming Consistency5/5

All 30 tool names use lowercase snake_case with a consistent domain-prefix convention such as market_, flow_, research_, sentiment_, and catalysts_, making the surface predictable. Even helpers like utc_time and risk_position_size fit the same noun-oriented pattern without style mixing.

Tool Count2/5

At 30 tools this set crosses the 'too many' threshold, and several tools reproduce data already available through broader ones such as research_token_view and market_quotes. The breadth is defensible for a crypto-research platform, but the surface feels heavy and could be consolidated.

Completeness5/5

The tool set covers the read-only crypto research workflow thoroughly: market data, candles, derivatives, funding, OI, order book, whale flows, ETF flows, on-chain metrics, news, sentiment, prediction odds, technicals, regime/positioning scans, and position sizing. It also includes health and UTC helpers that close practical workflow gaps, with no obvious dead ends.

Resources