Skip to main content
Glama
Sign In

qmax

by io.github.profitphil
OverviewDiscussionsAdmin

One QSwap pool in detail, with a deposit estimate

qmax_pool_detail
Read-onlyIdempotent

One pool's numbers explained, and for a deposit size (position_qu, the QU value of both sides together) an estimate of fees per day, per 30 days and the impermanent loss for price moves of 10%, 25% and 50%. Adding and removing liquidity each cost a flat 100,000 QU.

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": {
      "asset": "<asset>"
    },
    "name": "qmax_pool_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesAsset symbol, for example CFB or QDOGE (case does not matter). qmax_list_assets lists the tradable symbols.
windowNoThe period fee yield is measured over7d
position_quNoA deposit size to estimate for: the QU value of both sides together

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / position_qu / description
      Added value: +"A deposit size to estimate for: the QU value of both sides together"
    • addedInput schema / properties / window / description
      Added value: +"The period fee yield is measured over"
  2. Changed1 schema field changed
    • changedInput schema / properties / asset / description
      Previous value: -"Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one."New value: +"Asset symbol, for example CFB or QDOGE (case does not matter). qmax_list_assets lists the tradable symbols."
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare it a safe idempotent read. The description adds real value beyond them: it discloses the output dimensions returned (fees per day, per 30 days, IL at three price shocks) and a concrete cost constraint — a flat 100,000 QU each way for adding and removing liquidity — which materially affects deposit decisions.

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?

Two dense sentences with almost no waste, front-loading the resource and then the estimate payload. The opening clause 'One pool's numbers explained' is slightly vague padding before the concrete specifics, but the rest earns its place.

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 does the necessary work of enumerating the returned metrics and the round-trip liquidity cost. Gaps remain around behavior when position_qu is absent and how the window affects the estimates, but nothing critical to invoking it correctly is missing.

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 coverage is 100%, so the baseline of 3 applies. The parenthetical restating position_qu as 'the QU value of both sides together' mirrors the schema text, and the window parameter (7d/30d fee-yield period) is not addressed in the description at all, so no meaning is added beyond the schema.

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 specific resource (one QSwap pool's numbers) and a specific added capability (deposit-size fee and impermanent-loss estimates at 10/25/50% price moves). It is clearly distinguishable from list/get-pool siblings by the estimate feature, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool to call when it needs yield/IL projections for a prospective deposit. There is no explicit when-not guidance, no mention of what happens if position_qu is omitted, and no routing to qmax_get_liquidity_pool for raw pool state.

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

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