Skip to main content
Glama
Sign In
pathiel

pathiel

by Julian-dev28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_account

Read-only

Retrieve account equity, withdrawable funds, open positions, leverage, and liquidation distance in one call to assess balance and liquidation risk for a configured wallet or any address.

Instructions

Get the account's money in one call: total equity across the main perp dex, every HIP-3 dex and spot USDC, withdrawable, whether it can trade (and what blocks it), open positions in brief, plus risk: account leverage, cross margin ratio (1.0 = liquidation) and distance to liquidation. detail=full adds PnL per window (day, week, month, all time), the fee tier and API rate-limit use, for the configured account only. address reads any wallet instead. Use for balance and liquidation-risk questions. For each position in detail use get_positions; for what the risk profile allows use get_risk_limits. Needs a configured account or an address, never a key; with neither it returns {error, no_account: true}. Returns {account, risk}, plus {pnl, fees, rate_limits} with detail=full (ignored with address).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNosummary: equity, margin, risk. full: also PnL history, fees, rate limits (configured account only).summary
addressNoAny 0x address to read instead of the configured account (read-only; needs no key).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.6/5.0
Behavior4/5

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

Beyond readOnlyHint=true, it discloses the auth model (never a key; address is read-only), the failure shape ({error, no_account: true}), and a non-obvious interaction where detail is ignored when address is supplied. It does not mention pagination or freshness/latency of the equity figures, which would have pushed it higher.

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?

It is front-loaded with the core capability and ends with the return shape, with no filler sentences. The single dense paragraph packs many clauses together, which slightly hurts scanability for an agent parsing it quickly.

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?

With no output schema, the description fully specifies the return structure ({account, risk} plus {pnl, fees, rate_limits} under detail=full), the precondition, and the error case. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: detail=full expands the payload with PnL windows, fee tier and rate-limit use, and that detail is ignored when address is passed. That precedence rule is the key behavioral detail an agent needs and is absent from the schema.

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 opens with a specific verb and resource ('Get the account's money in one call') and then enumerates the concrete contents: total equity across the main perp dex, HIP-3 dexes and spot USDC, withdrawable, tradability and blockers, brief positions, and risk metrics. It explicitly separates itself from get_positions (per-position detail) and get_risk_limits (what the risk profile allows).

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?

It states the use case directly ('Use for balance and liquidation-risk questions') and names two siblings with the conditions that select them instead. It also states the precondition (configured account or address, never a key) and the fallback behavior when neither is present.

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