Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

pulse_trader_performance

Compare a trader's 30-day vs all-time PnL, trade count, win rate, and trend direction to assess if they are improving or cooling off.

Instructions

Get performance comparison for a trader: 30-day vs all-time PnL, trade count, win rate, and trend direction (improving/declining/stable). Use this to evaluate if a trader is currently hot or cooling off.

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:437-450 (handler)
    The tool 'pulse_trader_performance' is defined, registered, and its handler is implemented here. It takes 'useToonFormat' and 'address' (Ethereum wallet) parameters, calls the API at '/pulse/trader/{address}/performance', and formats the result. This single location serves as registration, schema, and handler all in one.
    // ══════════════════════════════════════════════════════════
// TOOL 8: Trader Performance
// ══════════════════════════════════════════════════════════
if (shouldRegister("pulse_trader_performance")) server.registerTool(
  "pulse_trader_performance",
  {
    description: "Get performance comparison for a trader: 30-day vs all-time PnL, trade count, win rate, and trend direction (improving/declining/stable). Use this to evaluate if a trader is currently hot or cooling off.",
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      address: ethAddressSchema,
    },
  },
  async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/performance`))
);

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It describes the output metrics but does not mention data freshness, rate limits, or what happens if the trader has no 30-day data. A baseline score of 3 is appropriate as it is a simple read operation.

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?

The description is two sentences long, with the first sentence stating the purpose and metrics, and the second providing a usage suggestion. It is front-loaded, concise, and contains no unnecessary words.

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 there is no output schema, the description adequately lists the return fields (30-day vs all-time PnL, trade count, win rate, trend direction). It does not cover edge cases or data structure details, but for a simple comparison tool, it provides sufficient context for an agent.

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 has 100% coverage with descriptions for both parameters (address and useToonFormat). The description adds context by explaining the return metrics, which indirectly clarifies the need for the address. However, it does not add significant meaning beyond the schema, so a baseline score of 3 is given.

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 retrieves a trader's performance comparison with specific metrics (30-day vs all-time PnL, trade count, win rate, trend direction). The verb 'Get' and resource 'performance comparison for a trader' are specific, and the tool is distinct from sibling trader-related tools.

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 includes a direct usage suggestion: 'Use this to evaluate if a trader is currently hot or cooling off.' This provides clear context for when to use the tool. It does not explicitly mention when not to use it or alternative tools, but the purpose is well-defined.

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