Skip to main content
Glama
Sign In

leverage

by xyz.spiralstake
OverviewDiscussionsAdmin

Get Positions

get_positions
Read-only

Read a wallet's open/closed Spiral leverage positions from chain state (read-only). For each: collateral/loan, leveraged collateral, net equity, debt, current LTV vs liquidation LTV (with headroom), current leverage, net USD value, and current leveraged APY. No cost-basis / realized P&L (those need off-chain history). Newest first. equityPositions lists the wallet's open equity vaults (stock leg + the yield loop(s) it funds); those loops are excluded from positions.

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": {
      "userAddress": "<userAddress>"
    },
    "name": "get_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoChain to target. Supported: 1, 4663. Default: 1.
userAddressYesWallet address to read positions for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations provide readOnlyHint=true, and the description reaffirms and expands on this by detailing exactly what is returned (collateral/loan, LTV, APY, etc.), what is excluded (cost-basis/P&L), ordering (newest first), and the relationship to equityPositions. This adds substantial behavioral context beyond the annotation.

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?

The description is efficiently structured: it leads with the verb and resource, lists the key return fields, notes exclusions, states ordering, and clarifies related terms. Each sentence earns its place with no redundancy, and the length is justified given the number of details conveyed.

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?

Despite lacking an output schema, the description fully enumerates the returned data fields, ordering, exclusions, and the distinction between positions and equityPositions. For a read-only tool with only two simple parameters, this is a complete and self-sufficient description that leaves no critical ambiguity.

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 description coverage is 100%, and both parameters have clear descriptions (chainId with supported values and default, userAddress for the wallet). The tool description does not add any additional meaning to the parameters beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 states a specific verb ('Read') and resource ('wallet's open/closed Spiral leverage positions'), and distinguishes itself from transaction-building siblings. It clearly differentiates between 'positions' and 'equityPositions', making the tool's scope unambiguous.

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

Usage Guidelines4/5

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

The description implies when to use the tool (to read position data) and explicitly states when not to use it (when cost-basis or realized P&L is needed, as those require off-chain history). It clarifies that equityPositions is separated from positions, guiding proper interpretation. It does not name alternative sibling tools explicitly, but the context makes the usage clear.

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

All leverage toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources