Skip to main content
Glama

cluster_feed_lite

Read-onlyIdempotent

FREE lite cluster board: tokens with active cluster events right now (address, symbol, consensus score, signal, tracked buyer count only — net flow, sellers, safety and canonical detail are capped). The full cluster_feed board adds the detail.

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_lite"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Beyond the annotations, the description adds useful behavioral context by listing included fields and noting that net flow, sellers, safety, and canonical detail are capped. It does not describe return format, pagination, freshness mechanics, or any rate limits, so it adds some but not rich behavioral detail.

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?

The description is two compact sentences with the core purpose and field limitations front-loaded. Every phrase contributes to identifying the tool or its capped scope, with no unnecessary digressions.

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?

For a simple no-parameter, read-only board without an output schema, the description supplies the essential return scope and explicitly names capped fields. It could be more complete with return format or freshness details, but it is largely sufficient given the rich safety annotations.

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?

The tool has zero parameters, so there are no parameter semantics to explain and the baseline score is 4. The description appropriately focuses on output scope instead of inventing parameter guidance.

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 clearly identifies the resource: a lite cluster board of tokens with active cluster events right now, and it lists the included fields. It also explicitly contrasts with the full cluster_feed board, though it does not directly differentiate from cluster_check alternatives.

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?

It implies this is the limited/free alternative and that cluster_feed adds detail, giving some context for choosing between them. However, it does not explicitly state when to use this tool versus the full board or cluster_check tools, leaving usage choices partly inferred.

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.