Skip to main content
Glama
Sign In
Limitless MCP

Limitless MCP

by PaulieB14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_trader_positions

Retrieve a trader's current positions, balances, and PnL across market types using their wallet address.

Instructions

Get a trader's current positions across both market types with balances and PnL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "get_trader_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesTrader wallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions specific return data (balances, PnL) which helps, but omits details on data freshness, authentication requirements, or position status (open vs closed).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single efficient sentence (12 words) with no redundancy. Front-loaded with action ('Get...positions') and back-loaded with return details ('balances and PnL'). Slightly terse given lack of output schema.

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?

Appropriate for low complexity (1 param, flat schema). Compensates for missing output schema by specifying return contents (balances, PnL). Could clarify what 'both market types' refers to given sibling tools don't explicitly mention market types.

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 the 'address' parameter fully documented. Description implies the parameter identifies the trader ('trader's positions') but doesn't explicitly reference the wallet address requirement or validate the parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb+resource ('Get...positions') and specifies key return data ('balances and PnL'). Distinguishes from sibling get_market_positions by focusing on 'trader' scope and 'both market types', though 'Get' is slightly generic.

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

Usage Guidelines2/5

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

No explicit when-to-use or alternative suggestions. However, 'across both market types' implicitly defines scope, distinguishing it from market-specific tools like get_market_positions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools