Limitless MCP

get_trader_profile

Retrieve a trader's complete profile from on-chain data, including trade count, volume, fees, PnL, and activity timestamps across both simple and negrisk markets.

Instructions

Get a trader's profile across both simple and negrisk markets. Shows trade count, volume, fees, PnL, and first/last trade timestamps from on-chain data.

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_profile"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Trader wallet address

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 24, 2026

TDQS

A3.8/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. Discloses data source ('on-chain data') and market coverage. However, lacks details on error handling (e.g., unknown address), caching behavior, or rate limits that would be expected for a data retrieval tool with no annotation safety hints.

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 well-structured sentences. Front-loaded with the action verb. First sentence establishes scope; second lists specific returned metrics. No redundant words or repetition of structured data elements.

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?

Compensates well for missing output schema by enumerating return fields (trade count, volume, fees, PnL, timestamps). Sufficient for a single-parameter lookup tool. Deducted one point for not describing error cases or empty result behavior.

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 already described as 'Trader wallet address'. The description aligns by referencing 'trader' and 'on-chain data' but adds no additional format constraints (e.g., checksum requirements) or usage guidance beyond the schema definition.

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?

States specific action ('Get'), resource ('trader's profile'), and scope ('across both simple and negrisk markets'). Distinguishes from siblings like get_trader_trades and get_trader_positions by specifying aggregated output fields (trade count, volume, fees, PnL) rather than individual records.

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?

Implicitly guides via listed output fields (use when needing aggregated stats), but lacks explicit when/when-not guidance or named alternatives. Does not clarify when to prefer this over get_top_traders or get_trader_positions despite clear functional overlap.

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

Deploy Server