Skip to main content
Glama

cluster_feed

Read-onlyIdempotent

Full cluster board: the tokens with ACTIVE tracked-wallet cluster events right now, ranked by consensus score. Candidates come from DexScreener's public attention feeds (boosts + latest profiles, Solana) plus registered narrative canonicals; each candidate is cluster-scanned live and only tokens with real tracked-wallet activity make the board. Per token: consensus score, signal, tracked buyers/sellers, tracked net USD, safety band, canonical status. An empty board is a real answer — it means no cluster events were detected in the current candidate set, not an error. This is the in-loop product: poll it to catch convergence as it forms. Cost: $0.02 USDC per call via x402 — no API key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark it read-only and idempotent, yet the description adds substantial context beyond them: cost of $0.02 USDC per call via x402, no API key required, live cluster-scanning of each candidate, and the non-obvious fact that an empty board is a valid answer rather than an error. That empty-result semantics note is exactly the kind of behavioral disclosure annotations cannot carry.

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 resource and ranking, then sources, then per-token fields, then the empty-board caveat and cost. Every sentence carries information, though the candidate-sources sentence is dense and the per-token field list could arguably be trimmed given no output schema exists.

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?

For a read-only, no-parameter board tool with no output schema, the description covers what appears on the board, where candidates come from, what an empty result means, and the cost model. Nothing an agent needs in order to call it or interpret its result is left implicit.

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?

There are zero input parameters, so there is nothing for the schema to document and no parameter ambiguity to resolve. The description correctly spends no words on inputs and instead documents the per-token output fields, which is the right allocation for a no-arg tool.

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?

States a specific resource and scope: a 'Full cluster board' of tokens with ACTIVE tracked-wallet cluster events, ranked by consensus score. The word 'Full' implicitly distinguishes it from the lite siblings, but no sibling is named explicitly, so differentiation is by adjective rather than direct comparison.

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?

'This is the in-loop product: poll it to catch convergence as it forms' gives a clear when-to-use posture (repeated polling for live convergence). It does not state when to prefer cluster_feed_lite or cluster_check, nor any exclusions, so it stops short of full alternative routing.

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.