Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_trader_closed_position_stats

Analyze a trader's closed positions: average hold time, win rate by position, total closed positions, and PnL summary. Determine if the trader is a scalper or swing trader.

Instructions

Get aggregate statistics about a trader's closed positions: average hold duration, win rate by position (not by fill), total positions closed, and PnL summary. Use this to understand how long a trader typically holds and their position-level performance. Answers: 'What is this trader's average hold time?', 'Win rate by position (not by fill)?', 'Is this trader a scalper or swing trader?', 'Average PnL per position?'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
addressYesEthereum wallet address (0x...)

Implementation Reference

  • The handler function for pulse_trader_closed_position_stats. It takes useToonFormat and address parameters, then calls the Coinversa API at /pulse/trader/{address}/closed-positions/stats to return aggregate statistics about a trader's closed positions.
      async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/closed-positions/stats`))
    );
  • Input schema for pulse_trader_closed_position_stats. Accepts useToonFormat (boolean, default true) for compact toon format, and address (Ethereum address regex-validated).
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        address: ethAddressSchema,
      },
    },
  • src/index.ts:877-887 (registration)
    Registration of the pulse_trader_closed_position_stats MCP tool. Conditionally registered via shouldRegister() which checks if an API key is present or if the tool is in the free-tier set (it is NOT in FREE_TIER_TOOLS, so it requires an API key).
    if (shouldRegister("pulse_trader_closed_position_stats")) server.registerTool(
      "pulse_trader_closed_position_stats",
      {
        description: "Get aggregate statistics about a trader's closed positions: average hold duration, win rate by position (not by fill), total positions closed, and PnL summary. Use this to understand how long a trader typically holds and their position-level performance. Answers: 'What is this trader's average hold time?', 'Win rate by position (not by fill)?', 'Is this trader a scalper or swing trader?', 'Average PnL per position?'",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          address: ethAddressSchema,
        },
      },
      async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/closed-positions/stats`))
    );
Behavior4/5

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

With no annotations, description carries full burden. It clarifies win rate is 'by position (not by fill)' and lists specific statistics. Does not disclose data freshness or limits, but for a stats tool, behavior is well-scoped. A 4 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise: two sentences plus bullet-like questions. No redundant information. Front-loaded with purpose followed by specific usage guidance.

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 tool has only two simple parameters, no output schema, and no nested objects, the description fully covers purpose, usage, and key behavioral details. Answers likely agent questions about returned metrics.

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% with parameter descriptions. Description adds value by mapping output to questions, aiding parameter context. For example, explaining that the tool returns average hold time, win rate, etc., enriches understanding of what 'address' parameter will produce.

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?

Description clearly states 'Get aggregate statistics about a trader's closed positions' and lists specific metrics (average hold duration, win rate by position, total positions closed, PnL summary). It distinguishes from sibling tools like 'pulse_trader_closed_positions' and 'pulse_trader_daily_stats' by focusing on aggregated position-level stats.

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 states when to use: 'Use this to understand how long a trader typically holds and their position-level performance.' Provides concrete questions it answers, guiding the agent to appropriate context. No exclusion of alternatives needed given clarity.

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