TRDEFI Liquidity

Open positions

trdefi_positions

Read-onlyIdempotent

Live non-custodial liquidity, as positions an agent can actually trade against. Each row carries the strategy hash, network, pair, tokens, settled volume and a quote_eligible flag, meaning the position is router-attached and its network has a quote route. It does NOT mean the position will quote: a maker can still gate it. Use this before a swap to find a real on-chain counterparty, or to survey where liquidity sits. Filter by network and by pair. Free, no key, no custody.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trdefi_positions"
  }
}

Input Schema

Name	Required	Description
`pair`	No	Pair filter. Either an exact pair such as "USDC/USDT", or a substring such as "USDC" or "WETH" which matches any pair containing it, or a network name, or part of a strategy hash.
`chain`	No	Network key, e.g. "base" or "ethereum". Defaults to every network.
`limit`	No	Rows to return.
`quote_ready`	No	True returns positions on a network that has a quote route, which is the quote_eligible set. False returns the positions that do not, which are usually on networks with no quote RPC. Neither guarantees a price: a maker can still gate a position, and around 6 in 10 sampled positions answer "Strategy is gated".

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / pair / description

Previous value: -"Pair filter, a substring match, e.g. \"USDC\" or \"WETH\". Omit for every pair."New value: +"Pair filter. Either an exact pair such as \"USDC/USDT\", or a substring such as \"USDC\" or \"WETH\" which matches any pair containing it, or a network name, or part of a strategy hash."

changedInput schema / properties / quote_ready / description

Previous value: -"True returns only positions that can be simulated. False returns the positions that cannot."New value: +"True returns positions on a network that has a quote route, which is the quote_eligible set. False returns the positions that do not, which are usually on networks with no quote RPC. Neither guarantees a price: a maker can still gate a position, and around 6 in 10 sampled positions answer \"Strategy is gated\"."

Changed3 schema fields changedOct 11, 2026

changedInput schema / properties / pair / description

Previous value: -"Pair filter. Currently only the USDC/USDT stable pair is selectable."New value: +"Pair filter, a substring match, e.g. \"USDC\" or \"WETH\". Omit for every pair."

removedInput schema / properties / pair / enum
```
Removed value: -[
-  "usdc-usdt"
-]
```

addedInput schema / properties / quote_ready

Added value: +{
+  "description": "True returns only positions that can be simulated. False returns the positions that cannot.",
+  "type": "boolean"
+}

First observedSep 26, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description goes well beyond them: it explains what quote_eligible actually means, warns it does not guarantee a quote because a maker can gate a position, and quantifies that around 6 in 10 sampled positions answer 'Strategy is gated'. It also discloses non-custodial, free, and no-key access.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool returns and why it matters, and the gating caveat is placed where an agent will read it. It is somewhat dense and partially duplicates the quote_ready schema caveat, which costs a point.

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?

With no output schema, the description carries the burden of describing returns and does so explicitly: strategy hash, network, pair, tokens, settled volume, and the quote_eligible flag. Combined with the filters and the gating caveat, an agent has everything needed to call and interpret this correctly.

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 the schema already documents all four parameters in depth, including the pair substring/strategy-hash matching and the quote_ready caveat. The description only restates 'filter by network and by pair', adding no syntax or edge-case detail beyond the schema, so 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?

States a specific resource (live non-custodial liquidity positions) and enumerates the returned row fields, so an agent knows exactly what it gets back. It does not name a sibling tool, so the boundary against trdefi_position_detail (per-position detail) is only inferable from the word 'positions' being plural, not stated.

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 concrete usage contexts: 'Use this before a swap to find a real on-chain counterparty, or to survey where liquidity sits.' It also names the filters available. It stops short of explicit when-not-to-use or a direct pointer to trdefi_quote/trdefi_position_detail.

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?