TRDEFI Liquidity

Position inventory

trdefi_position_inventory

Read-onlyIdempotent

Whether one position can actually be filled right now: the balance sitting in the strategy, the maker wallet balance behind it, and the remaining allowance, read from the chain. An Aqua virtual balance is a bookkeeping ceiling, not a reserve, so a position can answer a quote while the wallet behind it is empty - and the swap then reverts at the pull. Check this before signing a swap against a position that matters: fillable=false means the quote is real but the fill is not. Read-only, free, no key, and no dependency on 1inch rate limits.

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": {
      "hash": "<hash>"
    },
    "name": "trdefi_position_inventory"
  }
}

Input Schema

Name	Required	Description	Default
`hash`	Yes	Strategy hash, 64 hex characters.
`overview`	No	Also fetch 1inch's overview (status, openedAt, price range). Costs the upstream rate limit, so it is off by default.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only annotations, it explains the key behavioral risk: an Aqua virtual balance is a bookkeeping ceiling, not a reserve, so a quote can succeed while the wallet behind it is empty and the swap reverts at pull. It also adds operational context such as read-only, free, no key, and no 1inch rate-limit dependency.

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 purpose is front-loaded, and each sentence adds useful information: what is read, why fillability matters, when to check it, and what fillable=false means. There is no filler or repetition.

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?

For a two-parameter read-only tool with no output schema, the description is complete enough: it identifies the data returned, explains the fillability implication, and covers safety and rate-limit context. The schema already handles parameter details.

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%, so both the hash and overview parameters are already documented in the schema. The description does not add parameter-specific meaning beyond what the schema provides, making the baseline score 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 purpose: checking whether a position can actually be filled right now by reading strategy balance, maker wallet balance, and remaining allowance from chain. It clearly distinguishes this fillability check from a quote by explaining that a quote can exist while the fill still reverts.

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?

It gives a clear usage condition: check this before signing a swap against a position that matters, especially when fillable=false would mean the quote is real but the fill is not. It does not explicitly name alternatives or when-not-to-use cases, so it falls short of the top score.

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

All TRDEFI Liquidity 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?