Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_cross_market_asset

Aggregate per-venue long/short positions, notional, net bias, and leverage for any crypto asset, plus cross-venue totals. Use biasRange to detect venue disagreement. Accepts canonical names or synonyms.

Instructions

Cross-market aggregation for one asset: per-venue long/short positions, notional, net bias, unique wallets, leverage, plus a cross-venue total. Also returns biasRange (max-min netBias across venues) to detect disagreement. Accepts canonical names or synonyms (e.g. PAXG resolves to GOLD). Use when the user asks 'is gold crowded?', 'do different dexes disagree on BTC direction?', 'total OI on ETH across all venues?'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
canonicalYesCanonical asset name or synonym (e.g. 'GOLD', 'PAXG', 'BTC', 'HYPE'). The server resolves synonyms.

Implementation Reference

  • The handler function for the pulse_cross_market_asset tool. It takes a canonical asset name (or synonym) and calls the backend API at `/assets/{canonical}/cross-market` to return aggregated cross-market data (per-venue long/short positions, notional, net bias, unique wallets, leverage, cross-venue total, and biasRange).
      async ({ useToonFormat, canonical }) => {
        return toolResult(await callAPI(useToonFormat, `/assets/${encodeURIComponent(canonical)}/cross-market`));
      }
    );
  • Input schema for pulse_cross_market_asset: requires a 'canonical' string (min 1, max 40 chars) for the asset name or synonym, and an optional 'useToonFormat' boolean.
    {
      description: "Cross-market aggregation for one asset: per-venue long/short positions, notional, net bias, unique wallets, leverage, plus a cross-venue total. Also returns biasRange (max-min netBias across venues) to detect disagreement. Accepts canonical names or synonyms (e.g. PAXG resolves to GOLD). Use when the user asks 'is gold crowded?', 'do different dexes disagree on BTC direction?', 'total OI on ETH across all venues?'.",
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        canonical: z.string().min(1).max(40).describe("Canonical asset name or synonym (e.g. 'GOLD', 'PAXG', 'BTC', 'HYPE'). The server resolves synonyms."),
      },
    },
  • src/index.ts:331-343 (registration)
    Registration of the pulse_cross_market_asset tool with the MCP server. Conditionally registered via shouldRegister() — it is NOT in the FREE_TIER_TOOLS set, so it requires an API key to be available.
    if (shouldRegister("pulse_cross_market_asset")) server.registerTool(
      "pulse_cross_market_asset",
      {
        description: "Cross-market aggregation for one asset: per-venue long/short positions, notional, net bias, unique wallets, leverage, plus a cross-venue total. Also returns biasRange (max-min netBias across venues) to detect disagreement. Accepts canonical names or synonyms (e.g. PAXG resolves to GOLD). Use when the user asks 'is gold crowded?', 'do different dexes disagree on BTC direction?', 'total OI on ETH across all venues?'.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          canonical: z.string().min(1).max(40).describe("Canonical asset name or synonym (e.g. 'GOLD', 'PAXG', 'BTC', 'HYPE'). The server resolves synonyms."),
        },
      },
      async ({ useToonFormat, canonical }) => {
        return toolResult(await callAPI(useToonFormat, `/assets/${encodeURIComponent(canonical)}/cross-market`));
      }
    );
Behavior4/5

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

With no annotations, the description fully discloses return data (positions, notional, etc.) and mentions synonym resolution. It doesn't cover rate limits or authentication, but for a read tool this is sufficient.

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, no wasted words, front-loaded with core purpose. Every sentence adds value.

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's moderate complexity and absence of output schema, the description adequately covers what the tool returns and how to use it, leaving no critical gaps.

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?

The description adds significant meaning beyond the schema by explaining that canonical accepts synonyms and that useToonFormat controls output format, complementing the 100% schema coverage.

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 performs cross-market aggregation for one asset, listing per-venue metrics and a cross-venue total, and explicitly mentions use cases like 'is gold crowded?'.

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?

Provides explicit use cases with example queries, helping the agent understand when to invoke this tool. However, it does not mention when not to use or name specific sibling alternatives.

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