Skip to main content
Glama

LoomDesk

by trade.loomdesk
OverviewDiscussionsAdmin

A token's pools a position can go in

ladder_pools
Read-onlyIdempotent

Lists the pools of one token a ladder can be built in, in the order the site offers them: real markets that pay their liquidity first, then markets whose launchpad hook keeps the whole fee, then small ones. Use before plan_ladder, plan_limit_order or plan_build to choose a pool, or with quote to learn whether a pair exists. Returns: token, pools[] with pool (id), version, pair, quote, swapFeePct, hook, tickSpacing, stepPct, paysLiquidity, usdToMovePrice2Pct, volume24hUsd, fees24hUsd, weeklyFeesOnLiquidityPct, untraded, note; pairsThatExist; with quote, forQuote (its pools, and a verdict: build in it, or plan_build opens one). The first pool is the default. Behavior: read-only; the same token is read at most every 15 seconds; costs 1 unit. Errors: refused when the address is not a token the index knows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quoteNoETH, USDG, or a quote token's address: the pair asked about. The answer then says whether that exact pair has a pool, or that plan_build opens one.
tokenYesThe token's address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / quote / description
      Previous value: -"ETH, USDG or an address: the pair asked about; the answer then says whether that exact pair has a pool, or that plan_build opens one"New value: +"ETH, USDG, or a quote token's address: the pair asked about. The answer then says whether that exact pair has a pool, or that plan_build opens one."
    • addedInput schema / properties / token / description
      Added value: +"The token's address."
  2. Changed1 schema field changed
    • addedInput schema / properties / quote
      Added value: +{
+  "description": "ETH, USDG or an address: the pair asked about; the answer then says whether that exact pair has a pool, or that plan_build opens one",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description goes further with genuinely non-structured behavior: the 15-second per-token read throttle, the 1-unit cost, and the refusal error when the address is not indexed. It also explains ordering semantics and what the first pool means (default).

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 purpose and usage, with behavior and error info grouped at the end. The return-field enumeration is long, but it is justified since there is no output schema; still, the dense field dump slightly hurts scanability.

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 return-value burden and does so thoroughly (full pool field list, pairsThatExist, quote-mode output). Combined with rate-limit, cost, and error disclosure, 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds real meaning by explaining what supplying 'quote' does to the result (forQuote with a build/verdict outcome) and by noting the first pool is the default. It stops short of adding syntax beyond the schema, so not a 5.

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 ('Lists the pools of one token a ladder can be built in') and adds the ordering rule (real markets, launchpad-hook markets, small ones), which distinguishes it from siblings like arena_pools and market_tokens. An agent can tell what this returns without opening the schema.

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

Usage Guidelines5/5

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

Explicitly names when to use it: 'Use before plan_ladder, plan_limit_order or plan_build to choose a pool, or with quote to learn whether a pair exists.' It ties each usage mode to a concrete sibling tool, leaving nothing to inference.

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

All LoomDesk 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