Retrieve a complete perpetual account snapshot for an address or the configured wallet, including open orders, recent fills, positions, margin, and voucher eligibility.
Full perp account snapshot for an address (defaults to the server wallet): open orders, recent fills, open positions, margin account and paper-USDso voucher eligibility.
| Name | Required | Description | Default |
|---|---|---|---|
| address | No | Account address; defaults to the configured wallet |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears the full burden; it usefully discloses the default server-wallet behavior and the categories of data returned. However, it does not explicitly state read-only semantics, permission requirements, freshness, or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single front-loaded sentence that immediately identifies the resource and then enumerates returned data. There is no wasted framing or redundant text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read tool with no output schema, the description is nearly complete because it names the returned data categories and the default address behavior. It could be strengthened with explicit read-only or freshness/limit context, but no critical calling information is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is one optional parameter and the schema description coverage is 100%, including the same default-wallet behavior. The description reinforces the default but adds no syntax, formatting, or validation details beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific resource and scope: a full perp account snapshot for an address, defaulting to the server wallet. It clearly distinguishes this from market or order-action siblings by enumerating account-centric contents, though it does not explicitly name sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies usage by listing what the snapshot includes, but gives no explicit guidance on when to call this instead of siblings like claim_voucher or list_markets. There are no when-not conditions or alternatives mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.