Dexra

Check a real Orca LP position

lp_position_check

Read-onlyIdempotent

Read an actual Orca Whirlpools Position account: current tick range and signed distances, exact principal and latest unclaimed fees when boundary state is available, and bounded mint/vault risks. Supports official mutable and immutable programs and bundled Position accounts. Prices are token B per token A; amounts are gross before Token-2022 transfer fees. NFT mints, bundle roots, lifetime PnL/IL and rewards are not analyzed. Partial coverage is explicit; in range does not establish pool safety. Price: 0.030 USDC per call, included in subscriptions.

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": {
      "position": "<position>"
    },
    "name": "lp_position_check"
  }
}

Input Schema

Name	Required	Description	Default
`position`	Yes	Actual Orca Position account address, not an NFT mint, pool or bundle root

Output Schema

Name	Required	Description
`pool`	Yes
`range`	Yes	Prices are token B per one token A (null if required UI conversion is unavailable). Lower tick inclusive, upper exclusive. Signed nominal B/A boundary moves are 100*(boundary/current-1).
`reasons`	Yes
`summary`	Yes
`token_a`	Yes
`token_b`	Yes
`verdict`	Yes
`coverage`	Yes
`position`	Yes
`freshness`	Yes
`liquidity`	Yes
`pool_type`	Yes
`pool_risks`	Yes
`program_id`	Yes
`generated_at`	Yes
`position_mint`	Yes	Position NFT mint, or bundle mint for a bundled Position account; does not identify a wallet owner.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

The description adds real value beyond annotations: per-call pricing (0.030 USDC, included in subscriptions), unit conventions (prices are token B per token A, amounts gross before Token-2022 transfer fees), and explicit coverage caveats including that partial coverage is signalled. However, annotations already declare readOnly, idempotent and openWorld, and the description does not address error behavior for non-Position addresses or how partial-coverage results are surfaced in the response. Solid but not rich given the read-only annotation baseline.

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?

Front-loaded with the verb and resource, then capabilities, then units, then exclusions, then pricing. Dense but every clause carries actionable information an agent needs (unit orientation, fee treatment, coverage limits, cost per call).

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?

A single required parameter with a full output schema and read-only annotations means the description only has to cover scope, units, exclusions and cost, and it covers all of them explicitly, including the caveat that being in range is not evidence of pool safety.

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% and the single parameter is already documented with pattern and an exclusion note, so the schema does the heavy lifting. The description goes further by clarifying which account categories are accepted (official mutable/immutable program positions and bundled Position accounts), which meaningfully narrows valid input beyond the regex.

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?

States a specific verb and resource ('Read an actual Orca Whirlpools Position account') and enumerates the concrete outputs: tick range and signed distances, exact principal, latest unclaimed fees, and bounded mint/vault risks. It also names what it is not (NFT mints, bundle roots, pool or bundle root addresses), which separates it from clmm_range_stats and pool_health without opening a schema.

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?

Gives clear scope of applicability ('actual Position account', supporting official mutable and immutable programs and bundled Position accounts) and explicit exclusions (lifetime PnL/IL and rewards are not analyzed; in range does not establish pool safety). It does not name a specific sibling tool as the alternative, so the agent must infer the routing from the exclusions rather than being handed a direct pointer.

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

All Dexra tools Inspect

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

Need Help?