Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_lifecycles_recent

Retrieve the most recently closed position lifecycles across all wallets on Hyperliquid. Filter by coin, minimum notional, hold duration, and time window to analyze trade outcomes including MAE/MFE and liquidation flags.

Instructions

Global feed of the most recently CLOSED position lifecycles across ALL wallets — 'what just closed exchange-wide right now'. Reads the corrected position_lifecycles_full table: includes MAE/MFE (when backfilled), a liquidation flag, and optional spot. Cross-wallet successor to pulse_recent_closed_positions. Filter by coin, minNotional, hold-duration range, and time window. Note: the very freshest closes may not have MAE/MFE yet — the risk backfill lags real-time, so recent rows can show null MAE/MFE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
sinceNoTime window: e.g. '10m' (minutes), '1h' (hours), '1d' (days)1h
limitNoNumber of lifecycles to return.
coinNoFilter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER).
includeSpotNoInclude spot (@-prefixed) pairs. Default false (perps only).
minNotionalNoMinimum notional in USD (peak_size * entry_vwap), e.g. 100000 for $100K+ positions.
minDurationNoMinimum hold duration in milliseconds (e.g. 60000 for >= 1 minute).
maxDurationNoMaximum hold duration in milliseconds (e.g. 1000 for sub-second HFT).
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explicitly warns that MAE/MFE may be null for very recent closes due to risk backfill lag—an important behavioral trait. No contradictions with missing annotations. It could mention authentication needs or rate limits, but the transparency about data freshness is commendable.

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?

The description is 4 sentences, front-loaded with the core purpose and followed by relevant details (data source, behavior, filters, caveat). It is efficient but could be slightly tighter by merging the lineage note into the first sentence.

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?

Given no output schema and 8 parameters, the description explains the key output fields (MAE/MFE, liquidation flag, optional spot) and the data source. It also clarifies the useToonFormat parameter's impact on output format. This is adequate for an agent to understand what the tool provides.

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?

All 8 parameters have descriptions in the input schema (100% coverage), so baseline is 3. The description does not add significant per-parameter details beyond the schema; it provides overall context about the feed and the caveat about null MAE/MFE, but that is general context rather than parameter-level semantics.

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 clearly states the tool provides a global feed of recently closed position lifecycles across all wallets, explicitly distinguishing it as a cross-wallet successor to pulse_recent_closed_positions. The specific verb 'feed' and resource 'closed position lifecycles' combined with the scope 'across ALL wallets' makes the purpose unmistakable.

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

Usage Guidelines4/5

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

The description notes it is a cross-wallet successor to pulse_recent_closed_positions, providing alternative guidance. It also lists available filters (coin, minNotional, duration range, time window) which imply use cases. However, it does not explicitly state when not to use this tool or describe contraindications.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Coinversaa/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server