Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_trader_token_stats

Analyze a trader's performance per token, showing PnL, win rate, and volume for each coin. Identify which assets contribute to profit or loss.

Instructions

Get token-by-token P&L breakdown for any trader. Shows which coins they trade, their PnL per coin, win rate per coin, and volume per coin. Use to understand a trader's edge — e.g. 'this trader only makes money on ETH and loses on everything else.'

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

  • src/index.ts:802-814 (registration)
    Registration and handler for the 'pulse_trader_token_stats' tool. Registered via shouldRegister check, defines input schema (useToonFormat + ethAddress), and handler calls the API at `/pulse/trader/${address}/tokens`.
    // TOOL 21: Trader Token Stats
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("pulse_trader_token_stats")) server.registerTool(
      "pulse_trader_token_stats",
      {
        description: "Get token-by-token P&L breakdown for any trader. Shows which coins they trade, their PnL per coin, win rate per coin, and volume per coin. Use to understand a trader's edge — e.g. 'this trader only makes money on ETH and loses on everything else.'",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          address: ethAddressSchema,
        },
      },
      async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/tokens`))
    );
  • Handler function: async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/tokens`)). Calls the backend API to get token-by-token P&L breakdown for the given wallet address.
    async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/tokens`))
  • Input schema for pulse_trader_token_stats: accepts useToonFormat (boolean, default true) and address (Ethereum wallet address validated by ethAddressSchema regex).
    {
      description: "Get token-by-token P&L breakdown for any trader. Shows which coins they trade, their PnL per coin, win rate per coin, and volume per coin. Use to understand a trader's edge — e.g. 'this trader only makes money on ETH and loses on everything else.'",
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        address: ethAddressSchema,
      },
    },
Behavior4/5

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

The description explains what data is returned (per-coin breakdown) and implies a read-only operation. No annotations exist, so the description carries the burden, and it is sufficient without contradictions.

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?

Two targeted sentences with no filler. The first sentence defines the action and output; the second provides a concrete usage scenario.

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, the description adequately describes the return values. It does not cover error conditions or performance, but the tool is straightforward and the description is sufficient for an agent to understand what it does.

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?

Input schema has 100% description coverage. The description adds value by explaining the overall output structure and providing a usage example, going beyond the schema's parameter-level details.

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 it returns a token-by-token P&L breakdown for a trader, specifying the metrics (PnL, win rate, volume). This distinctively separates it from other trader-focused tools like pulse_trader_daily_stats or pulse_trader_performance.

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 provides a direct use case: 'understand a trader’s edge' with a concrete example. It does not explicitly mention when not to use or list alternatives, but the context of sibling tools makes the specialization clear.

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