Coinversaa Pulse

Official

by Coinversaa

Overview Schema Related Servers Score Discussions

JavaScript

Remote

market_positions

Fetch open positions for any wallet on Hyperliquid, displaying entries, sizes, unrealized PnL, and leverage.

Instructions

Get all open positions for any wallet address on Hyperliquid. Shows current entries, sizes, unrealized PnL, and leverage for each position.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`useToonFormat`	No	Return data in compact toon format (default: true). Set to false for standard JSON.
`address`	Yes	Ethereum wallet address (0x...)

Implementation Reference

src/index.ts:467-480 (registration)

Registration of the 'market_positions' tool using server.registerTool(). The tool is registered under the name 'market_positions' with a description and input schema requiring an Ethereum address.

// ══════════════════════════════════════════════════════════
// TOOL 10: Wallet Positions
// ══════════════════════════════════════════════════════════
if (shouldRegister("market_positions")) server.registerTool(
  "market_positions",
  {
    description: "Get all open positions for any wallet address on Hyperliquid. Shows current entries, sizes, unrealized PnL, and leverage for each position.",
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      address: ethAddressSchema,
    },
  },
  async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/market/positions/${address}`))
);

src/index.ts:479-480 (handler)
Handler for 'market_positions': calls the API endpoint /market/positions/{address} with the provided wallet address.
```
  async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/market/positions/${address}`))
);
```

src/index.ts:471-477 (schema)

Input schema for market_positions: accepts useToonFormat (boolean) and address (validated Ethereum address via ethAddressSchema regex).

"market_positions",
{
  description: "Get all open positions for any wallet address on Hyperliquid. Shows current entries, sizes, unrealized PnL, and leverage for each position.",
  inputSchema: {
    useToonFormat: useToonFormatSchema,
    address: ethAddressSchema,
  },

build/index.js:314-323 (registration)

Registration of the 'market_positions' tool in the built/compiled JS version (build/index.js). Same structure: registerTool with ethAddressSchema.

// TOOL 10: Wallet Positions
// ══════════════════════════════════════════════════════════
if (shouldRegister("market_positions"))
    server.registerTool("market_positions", {
        description: "Get all open positions for any wallet address on Hyperliquid. Shows current entries, sizes, unrealized PnL, and leverage for each position.",
        inputSchema: {
            useToonFormat: useToonFormatSchema,
            address: ethAddressSchema,
        },
    }, async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/market/positions/${address}`)));

build/index.js:323-323 (handler)

Handler in the built version: calls API at /market/positions/{address}.

}, async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/market/positions/${address}`)));

Tool Definition Quality

A3.8/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 cover behavioral traits. It describes a read operation (no mutation) and lists output fields, but does not disclose potential side effects, auth requirements, rate limits, or data freshness. Basic transparency is present.

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, concise and front-loaded. Every sentence adds value: the first states primary purpose, the second enumerates returned data. No wasted 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 no output schema, the description adequately explains the return values (entries, sizes, PnL, leverage). It defines scope ('open positions for any wallet address') and is sufficient for a simple read tool. However, it could mention the compact toon format parameter's effect or any limitations.

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 coverage is 100% with descriptions for both parameters ('address' and 'useToonFormat'). The tool description does not add additional meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 action ('Get'), the resource ('all open positions for any wallet address on Hyperliquid'), and the specific data returned (entries, sizes, unrealized PnL, leverage). It distinguishes itself from siblings like 'pulse_cohort_positions' by focusing on individual wallet addresses.

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 usage (any wallet address on Hyperliquid) but does not provide explicit guidance on when to use this tool over alternatives (e.g., pulse_cohort_positions). No when-not-to-use or exclusion criteria are mentioned.

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

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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