Skip to main content
Glama

TraderSpy

by app.traderspy

get_my_account

Read-only

Use this when the user asks about THEIR OWN TraderSpy account: Hyperliquid balance, open positions, unrealized PnL, or paper-trading account. Read-only — this connector cannot place, close or modify orders, and cannot withdraw. Requires a personal MCP connection (key from traderspy.app Settings).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
paperNoPaper trading account, when enabled
tradingNoConnector capabilities: read-only. States that this connector cannot place orders or withdraw, and where the user trades instead
balancesNo{ accountValueUsd, withdrawableUsd }
setupUrlNoWhere to create a wallet, returned only when hasWallet is false
hasWalletNoFalse when the user has not created a Hyperliquid wallet yet
positionsNoOpen Hyperliquid positions

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds concrete value by specifying what the tool cannot do (place, close, or modify orders, withdraw) and the required connection, which is beyond annotation coverage. No contradiction.

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, front-loaded with the primary usage condition, then supplemental constraints. Every sentence contributes useful information with no redundancy or filler.

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 simplicity (no parameters), the presence of an output schema (so return format is covered), and clear usage/constraint statements, the description is complete. It covers when to use, limitations, and prerequisites, leaving no significant 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 tool has zero parameters, so the description is the sole source of behavioral context. It clearly describes the account attributes covered (balance, positions, PnL, paper-trading), which is sufficient for an empty schema. Given no parameters, baseline 4 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 it retrieves the user's own TraderSpy account details (balance, positions, PnL, paper-trading), with the verb 'get' and resource 'my account'. It distinguishes itself from sibling tools like get_positions and get_trader_profile by emphasizing 'THEIR OWN' account, making it unambiguous.

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

Usage Guidelines5/5

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

Explicitly instructs when to use: 'Use this when the user asks about THEIR OWN TraderSpy account.' It also provides constraints (read-only, cannot place/modify orders, cannot withdraw) and a prerequisite (personal MCP connection), leaving no doubt about appropriate invocation.

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

All TraderSpy toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools are clearly distinct, targeting different data categories (market data, signals, traders, account). Some potential overlap exists between get_price, get_candles, and get_market_stats, but their descriptions clarify the specific use cases. Overall, an agent can differentiate them reliably.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with the verb 'get' and a descriptive noun (e.g., get_candles, get_signals, get_trader_profile). This uniform naming makes it very predictable for an agent.

Tool Count5/5

With 15 tools, the count is within the ideal range for a domain-specific server. Each tool serves a distinct purpose related to market data, signals, and trader analytics, and none feel redundant or extraneous.

Completeness4/5

The tool set covers core read operations for market data, signals, traders, and account info, which aligns with the apparent purpose of a data-provider server. Minor gaps include lack of write operations (e.g., placing trades) or historical signal details beyond individual IDs, but these are not critical for a data-oriented service.

Resources