pulse_cross_market_asset
Aggregate per-venue long/short positions, notional, net bias, and leverage for any crypto asset, plus cross-venue totals. Use biasRange to detect venue disagreement. Accepts canonical names or synonyms.
Instructions
Cross-market aggregation for one asset: per-venue long/short positions, notional, net bias, unique wallets, leverage, plus a cross-venue total. Also returns biasRange (max-min netBias across venues) to detect disagreement. Accepts canonical names or synonyms (e.g. PAXG resolves to GOLD). Use when the user asks 'is gold crowded?', 'do different dexes disagree on BTC direction?', 'total OI on ETH across all venues?'.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| useToonFormat | No | Return data in compact toon format (default: true). Set to false for standard JSON. | |
| canonical | Yes | Canonical asset name or synonym (e.g. 'GOLD', 'PAXG', 'BTC', 'HYPE'). The server resolves synonyms. |
Implementation Reference
- src/index.ts:340-343 (handler)The handler function for the pulse_cross_market_asset tool. It takes a canonical asset name (or synonym) and calls the backend API at `/assets/{canonical}/cross-market` to return aggregated cross-market data (per-venue long/short positions, notional, net bias, unique wallets, leverage, cross-venue total, and biasRange).
async ({ useToonFormat, canonical }) => { return toolResult(await callAPI(useToonFormat, `/assets/${encodeURIComponent(canonical)}/cross-market`)); } ); - src/index.ts:333-339 (schema)Input schema for pulse_cross_market_asset: requires a 'canonical' string (min 1, max 40 chars) for the asset name or synonym, and an optional 'useToonFormat' boolean.
{ description: "Cross-market aggregation for one asset: per-venue long/short positions, notional, net bias, unique wallets, leverage, plus a cross-venue total. Also returns biasRange (max-min netBias across venues) to detect disagreement. Accepts canonical names or synonyms (e.g. PAXG resolves to GOLD). Use when the user asks 'is gold crowded?', 'do different dexes disagree on BTC direction?', 'total OI on ETH across all venues?'.", inputSchema: { useToonFormat: useToonFormatSchema, canonical: z.string().min(1).max(40).describe("Canonical asset name or synonym (e.g. 'GOLD', 'PAXG', 'BTC', 'HYPE'). The server resolves synonyms."), }, }, - src/index.ts:331-343 (registration)Registration of the pulse_cross_market_asset tool with the MCP server. Conditionally registered via shouldRegister() — it is NOT in the FREE_TIER_TOOLS set, so it requires an API key to be available.
if (shouldRegister("pulse_cross_market_asset")) server.registerTool( "pulse_cross_market_asset", { description: "Cross-market aggregation for one asset: per-venue long/short positions, notional, net bias, unique wallets, leverage, plus a cross-venue total. Also returns biasRange (max-min netBias across venues) to detect disagreement. Accepts canonical names or synonyms (e.g. PAXG resolves to GOLD). Use when the user asks 'is gold crowded?', 'do different dexes disagree on BTC direction?', 'total OI on ETH across all venues?'.", inputSchema: { useToonFormat: useToonFormatSchema, canonical: z.string().min(1).max(40).describe("Canonical asset name or synonym (e.g. 'GOLD', 'PAXG', 'BTC', 'HYPE'). The server resolves synonyms."), }, }, async ({ useToonFormat, canonical }) => { return toolResult(await callAPI(useToonFormat, `/assets/${encodeURIComponent(canonical)}/cross-market`)); } );