Skip to main content
Glama

Corridor Heat — Flow Index

sv_flow
Read-only

Orkid corridor-heat telemetry: graph-router edge records aggregated per venue×chain×token corridor — edge count, executable depth (median/max/sum USD), median margin bps, first/last seen, span. Own listener-fleet data, not republished. Params: window_min (1–1440, default 240), venue (e.g. dln), min_depth (USD on depth_usd_max), limit (≤500). Free with X-ORKID-API-Key or $0.01 USDC/call via x402.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax corridors, default 50, cap 500
venueNoVenue filter, e.g. "dln"
min_depthNoMin depth_usd_max USD threshold
window_minNoTrailing window minutes, default 240, max 1440

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already mark this read-only, open-world, non-destructive; the description adds substantive context: data provenance ('own listener-fleet data, not republished'), returned aggregations, and access/payment terms (API key or $0.01 USDC via x402). It does not discuss rate limits or pagination beyond the limit cap, but the auth/cost/provenance disclosure is strong.

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?

Dense but front-loaded: purpose, aggregation grain, returned fields, provenance, params, and access terms appear in a compact sequence with little filler. The long compound sentence is efficient, though slightly hard to scan.

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 returned metrics and aggregation grain; it also covers the access model and parameter bounds. The main omission is decision guidance relative to sibling tools, but otherwise it is complete for a filtered telemetry query.

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 coverage is 100%, so all four parameters are already documented; the description mostly mirrors them, adding the window_min lower bound of 1 and clarifying that min_depth applies to depth_usd_max. That is incremental value rather than full semantic enrichment.

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 specific resource (corridor-heat telemetry) and defines the aggregation unit (venue×chain×token corridor) plus returned metrics, so the agent knows it is a corridor-level flow dataset. It does not explicitly compare against any sibling, but the specialized domain and 'not republished' provenance make it distinguishable.

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 or when-not guidance is given, and no alternative is named among the many siblings. The only usage signal is implied by the corridor-heat subject matter; an agent must infer whether to use this instead of sv_index_events or another analytics tool.

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