Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_recent_closed_positions

Retrieve recently closed positions from all traders on Hyperliquid. Filter by time window, coin, notional, or hold duration.

Instructions

Global feed of recently closed positions across all traders, from the legacy closed_positions table. SUPERSEDED by pulse_lifecycles_recent, which reads the corrected position_lifecycles_full table (adds MAE/MFE + spot coverage). Prefer pulse_lifecycles_recent; kept for backward compatibility.

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 positions to return
coinNoFilter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER)
minNotionalNoMinimum notional value in USD (e.g. 100000 for $100K+ positions)
minDurationNoMinimum hold duration in milliseconds (e.g. 60000 for positions held at least 1 minute)
maxDurationNoMaximum hold duration in milliseconds (e.g. 1000 for sub-second HFT trades, 60000 for under 1 minute)
Behavior3/5

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

No annotations are provided; the description carries the full burden. It states the data comes from a legacy table, implying potential staleness but does not explicitly declare read-only behavior or other safety characteristics.

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 concise, consisting of two sentences that cover purpose and deprecation. It is front-loaded with the primary purpose and then provides actionable guidance, though it could be slightly more structured.

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?

Given the lack of output schema and the presence of many sibling tools, the description effectively communicates the tool's role and its relationship to the preferred alternative, making it complete for decision-making.

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 input schema already provides 100% coverage for all 7 parameters with meaningful descriptions. The tool-level description does not add additional parameter semantics beyond what the schema offers.

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?

Clearly states it provides a global feed of recently closed positions across all traders. It also distinguishes itself from the sibling tool pulse_lifecycles_recent by noting it is superseded and why.

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

Usage Guidelines5/5

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

Explicitly advises to prefer pulse_lifecycles_recent over this tool and explains the reasoning (adds MAE/MFE + spot coverage). This provides clear when-to-use and when-not-to-use guidance.

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