Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Position Lifecycle Details

pulse_lifecycle
Read-onlyIdempotent

Fetch one position lifecycle by numeric ID and drill into every fill that built or closed it, including timestamp, side, size, price, PnL, fee, and transaction hash.

Instructions

Look up one position lifecycle by its numeric ID, including the trade fills that composed it (timestamp, side, size, price, PnL, fee, tx hash) joined from the trades table within the open->close window. Use after pulse_trader_lifecycles to drill into exactly how a single position was built and unwound. Fills are paged by the connector: fillsLimit (default 100, max 1000) and fillsOffset; the response carries fillCount (total fills in the lifecycle), fillsOffset, truncated and a note with the next offset. Lifecycles are a rolling 90-day window (closed within the last 90 days, plus open ones); see data_coverage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesLifecycle ID (from pulse_trader_lifecycles).
fillsLimitNoMax fills to return in this page (default 100, max 1000).
fillsOffsetNoFills to skip, for paging (default 0).
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / fillsLimit
      Added value: +{
+  "default": 100,
+  "description": "Max fills to return in this page (default 100, max 1000).",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / fillsOffset
      Added value: +{
+  "default": 0,
+  "description": "Fills to skip, for paging (default 0).",
+  "minimum": 0,
+  "type": "integer"
+}
  2. Addedv0.8.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: fills are joined from the trades table within the open->close window, paging is done by the connector, the response carries fillCount, fillsOffset, truncated and a note with the next offset, and the dataset is a rolling 90-day window. This is more than an agent could infer from structured fields.

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?

Front-loaded with the core lookup, then usage routing, then paging and window caveats — every sentence carries information. Minor redundancy: the fillsLimit default 100 / max 1000 detail duplicates the schema, and the run-on first sentence is dense.

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 no output schema, the description carries the return-value burden and does so: it enumerates fill fields, the paging metadata, and the truncation signal. It also discloses the 90-day rolling window and points to data_coverage for scope, so an agent has what it needs to call and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the type constraints: it explains that fillsLimit/fillsOffset drive connector-side paging, that truncated signals a partial page, and that a next-offset note is returned. It does restate fillsLimit's default/max, which the schema already gives.

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?

Opens with a specific verb and resource ('Look up one position lifecycle by its numeric ID') and immediately scopes the payload (the trade fills that composed it, with named fields). An agent can distinguish this single-lifecycle lookup from the sibling list tools like pulse_trader_lifecycles without opening a schema.

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?

Explicitly sequences the tool: 'Use after pulse_trader_lifecycles to drill into exactly how a single position was built and unwound,' naming the alternative and the condition that selects it. It stops short of stating when-not to use it (e.g., vs pulse_lifecycles_recent or pulse_trader_lifecycle_summary), so it is clear but not exhaustive.

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

Deploy Server

Other Tools