Skip to main content
Glama

TRDEFI Liquidity

by io.github.TRDEFI
OverviewDiscussionsAdmin

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 saying whether /api/quote can simulate 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairNoPair filter, a substring match, e.g. "USDC" or "WETH". Omit for every pair.
chainNoNetwork key, e.g. "base" or "ethereum". Defaults to every network.
limitNoRows to return.
quote_readyNoTrue returns only positions that can be simulated. False returns the positions that cannot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new context: it is free, needs no API key, involves no custody, and the quote_eligible flag tells the agent whether /api/quote can simulate a row — useful operational detail beyond the annotations.

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, then the fields, then the usage triggers and constraints. Four tight sentences with little waste, though "as positions an agent can actually trade against" is slightly promotional filler.

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?

With no output schema, the description usefully enumerates the returned row fields and explains the quote_eligible flag, and covers access constraints (free, no key, no custody). Pagination/limit behavior is left to the schema, which documents it adequately.

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 the schema already documents pair, chain, limit and quote_ready in full; the baseline is 3. The description only restates that filtering is by network and pair and gestures at the quote_eligible flag, adding no syntax or semantics the schema lacks.

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?

The description states a concrete resource — live non-custodial liquidity positions — and enumerates the row fields (strategy hash, network, pair, tokens, settled volume, quote_eligible), which makes the output concrete. It is clear what the tool returns, though it never explicitly names or contrasts the sibling tools (trdefi_position_detail, trdefi_quote) it sits beside.

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 explicit triggers: "Use this before a swap to find a real on-chain counterparty, or to survey where liquidity sits," plus the filtering affordances (network and pair). There is no when-not guidance and no named alternative for the narrower per-position or quote lookups.

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

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