Skip to main content
Glama

AINDEX

Liquidity, volume and momentum for tokens

get_token_market
Read-only

For up to 16 token addresses: price, liquidity and 24h volume summed over their pools, price change over 5m/1h/6h/24h, buys and sells, how many pools and when the first opened, the deepest pools, and (when known) holder count, top-10 holder share, GeckoTerminal's score and honeypot flag. Check liquidity before sizing any trade in a token you do not know.

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": {
      "tokens": "<tokens>"
    },
    "name": "get_token_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered and the description is not burdened with it. The description does add genuinely useful behavior: the aggregation rule ('summed over their pools'), a hard coverage cap of 16 addresses, and the honest caveat that some holder/score fields only appear 'when known', which warns of partial results. It does not disclose which chain(s) are covered, how fresh the data is, or what happens when an address has no pools.

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 the scope ('For up to 16 token addresses') followed by the returned metrics, then a closing imperative that tells the agent what to do with the answer. It is one dense enumeration sentence plus one action sentence, with no filler. Density is high but every listed metric earns its place because no output schema exists to carry 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 and only one input parameter, the description correctly absorbs the burden of describing return values, and it does so field by field, including conditional fields. A read-only, open-world fetch tool needs little else. The remaining gaps are chain identity and data freshness, which matter for trading decisions but are secondary to correct invocation.

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 description coverage is 0%, so the description must carry the parameter load, and it partially does: it clarifies the strings are token addresses (not pool addresses) and states the 16-item ceiling that mirrors maxItems. It does not state that addresses must be 0x-prefixed hex or which network the contracts live on, both of which the agent needs but the bare pattern implies. Net, it adds real meaning over an otherwise undescribed array.

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 definition names a specific verb and resource and then enumerates exactly which metrics are returned (liquidity, 24h volume, 5m/1h/6h/24h price change, buys/sells, pool count, deepest pools, holder stats, GeckoTerminal score, honeypot flag). This field list is specific enough to separate it from siblings like get_candles or get_v4_pool, though it never names or contrasts an alternative. It reads as a return-value inventory rather than an explicit 'returns X for Y' statement, which keeps it just under a 5.

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?

One concrete when-to-use condition is given: 'Check liquidity before sizing any trade in a token you do not know.' That is actionable guidance tied to a real workflow decision, not a filler sentence. However, there are no when-not conditions, no mention of when a batched call beats a single-address call, and no pointer to search_tokens or discover_tokens for address resolution.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources