Skip to main content
Glama
Sign In

qmax

by io.github.profitphil
OverviewDiscussionsAdmin

List or search tradable Qubic assets

qmax_list_assets
Read-onlyIdempotent

Lists assets that trade on QX and/or QSwap, most liquid first, or searches by symbol.

Gives each asset's symbol and which markets it trades on ('QX', 'QSwap' or both: only assets on both can be split for a better price).

Returns: { count, assets: [{ id, symbol, category ('contract' shares or 'token'), venues, priceQu, liquidityQu, activity }] }. Prices are QU per unit.

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": "qmax_list_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost assets to return
queryNoPart of a symbol to search for, e.g. 'QD'
categoryNoOnly smart-contract shares or only tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: default sort order ('most liquid first'), the meaning of venue membership ('only assets on both can be split for a better price'), and the exact return shape. It stops short of noting error or empty-result behavior.

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?

Three short, front-loaded blocks: what it does, what each result implies, then the return shape. No filler, and the ordering/pricing caveats are placed where an agent needs them.

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 needed work by spelling out the return object and price unit (QU). It is complete enough to call correctly, though pagination/truncation behavior at the limit cap is left to the schema alone.

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 all three parameters are already documented. The description only loosely reinforces them ('searches by symbol', the contract/token distinction in returns) and adds no syntax or format 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.

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 assets that trade on QX and/or QSwap') plus the alternate mode ('searches by symbol'). The scope (tradable assets, most liquid first) distinguishes it cleanly from siblings like qmax_list_pools and qmax_pool_detail.

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?

The description tells the agent that the tool serves two modes (list vs symbol search) and explains the market-coverage constraint needed to interpret results. However, it names no alternative tool and gives no explicit when-not guidance, so the routing decision is left partly to inference.

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