Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_hidden_gems

Discover high-performing traders overlooked by other platforms. Filter by win rate, PnL, and trade count to reveal skilled traders flying under the radar.

Instructions

Discover underrated high-performing traders who fly under the radar. Filters by minimum win rate, PnL, and trade count. These are skilled traders that most platforms don't surface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
minWinRateNoMinimum win rate percentage
minPnlNoMinimum total PnL in USD
minTradesNoMinimum number of trades
maxTradesNoMaximum number of trades (filters out well-known whales)
limitNoNumber of traders to return

Implementation Reference

  • src/index.ts:367-390 (registration)
    Registration of the 'pulse_hidden_gems' tool with input schema and handler. The tool discovers underrated high-performing traders by filtering on minWinRate, minPnl, minTrades, maxTrades, and limit. It calls the API endpoint /pulse/hidden-gems.
    if (shouldRegister("pulse_hidden_gems")) server.registerTool(
      "pulse_hidden_gems",
      {
        description: "Discover underrated high-performing traders who fly under the radar. Filters by minimum win rate, PnL, and trade count. These are skilled traders that most platforms don't surface.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          minWinRate: z.number().default(60).describe("Minimum win rate percentage"),
          minPnl: z.number().default(10000).describe("Minimum total PnL in USD"),
          minTrades: z.number().default(50).describe("Minimum number of trades"),
          maxTrades: z.number().default(500).describe("Maximum number of trades (filters out well-known whales)"),
          limit: z.number().min(1).max(100).default(20).describe("Number of traders to return"),
        },
      },
      async ({ useToonFormat, minWinRate, minPnl, minTrades, maxTrades, limit }) =>
        toolResult(
          await callAPI(useToonFormat, "/pulse/hidden-gems", {
            minWinRate: String(minWinRate),
            minPnl: String(minPnl),
            minTrades: String(minTrades),
            maxTrades: String(maxTrades),
            limit: String(limit),
          })
        )
    );
  • Input schema for pulse_hidden_gems: useToonFormat (bool), minWinRate (number, default 60), minPnl (number, default 10000), minTrades (number, default 50), maxTrades (number, default 500), limit (number, 1-100, default 20).
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      minWinRate: z.number().default(60).describe("Minimum win rate percentage"),
      minPnl: z.number().default(10000).describe("Minimum total PnL in USD"),
      minTrades: z.number().default(50).describe("Minimum number of trades"),
      maxTrades: z.number().default(500).describe("Maximum number of trades (filters out well-known whales)"),
      limit: z.number().min(1).max(100).default(20).describe("Number of traders to return"),
    },
  • Handler function for pulse_hidden_gems: validates inputs, then calls the Coinversa API at /pulse/hidden-gems with minWinRate, minPnl, minTrades, maxTrades, and limit as query parameters.
      async ({ useToonFormat, minWinRate, minPnl, minTrades, maxTrades, limit }) =>
        toolResult(
          await callAPI(useToonFormat, "/pulse/hidden-gems", {
            minWinRate: String(minWinRate),
            minPnl: String(minPnl),
            minTrades: String(minTrades),
            maxTrades: String(maxTrades),
            limit: String(limit),
          })
        )
    );
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions filters and the 'underrated' aspect, lacking details on data freshness, rate limits, or any side effects. The description is too brief for a tool with no annotations.

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 sentences efficiently convey purpose and key filters. No extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 6 parameters including a format toggle (useToonFormat), the description does not explain the output structure or the compact toon format. Among many sibling tools, more context on what's returned would improve completeness.

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?

Schema description coverage is 100% with clear parameter descriptions. The tool-level description merely summarizes filters ('minimum win rate, PnL, and trade count') without adding meaning beyond the schema. Baseline 3 applies.

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's purpose: discovering underrated high-performing traders. It distinguishes itself from siblings like pulse_leaderboard by emphasizing traders that 'fly under the radar' and are typically not surfaced.

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

Usage Guidelines3/5

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

The description implies when to use (to find hidden gems) but does not explicitly contrast with alternatives like pulse_leaderboard or pulse_biggest_trades. No when-not guidance is provided.

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