Skip to main content
Glama

Wallet open positions

wallet_positions
Read-onlyIdempotent

List a wallet's largest open positions by current value.

Accepts a 0x wallet address or an OrcaLayer nickname. Returns the positions with the largest current value first, in a compact form, plus a count of how many more are not shown.

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": "wallet_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many open positions to return, 1 to 50. The wallet may hold more; the response reports how many were left out.
addressYes0x wallet address (proxy or signer) or OrcaLayer nickname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"0x wallet address (proxy or signer) or OrcaLayer nickname."
    • addedInput schema / properties / limit / description
      Added value: +"How many open positions to return, 1 to 50. The wallet may hold more; the response reports how many were left out."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral facts: results are sorted largest-value-first, returned in a compact form, and include a count of omitted positions. It stops short of covering rate limits or refresh/caching behavior, which is why it is not a 5.

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?

Three short lines, front-loaded with the purpose, followed by accepted input forms and then return behavior. There is no filler, and each sentence contributes a distinct fact the agent needs.

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?

For a two-parameter read tool with full annotation coverage and no output schema, the description covers purpose, accepted inputs, ordering, and truncation semantics. The only soft spot is "compact form," which does not say which fields appear, but that is a minor omission given the tool's simplicity.

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%, so both the address/nickname duality and the 1–50 limit range are already documented in the schema. The description reinforces the truncation contract ("a count of how many more are not shown"), which matches the limit parameter's documented behavior, but adds no new syntax or format detail. Baseline 3 applies.

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?

"List a wallet's largest open positions by current value" gives a specific verb (list), resource (open positions), and ordering (by current value), so the agent knows exactly what comes back. It is clear enough to separate from a general overview, though it never explicitly contrasts itself with the sibling wallet_overview.

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?

The phrase "largest open positions" implies this is a ranked subset rather than a full dump, which hints at when to reach for it. However, there is no explicit when-to-use/when-not statement and no alternative named, so the agent must infer the boundary against wallet_overview or leaderboard.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.