Skip to main content
Glama

cluster_check_lite

Read-onlyIdempotent

FREE lite cluster & consensus report for one token (Solana mint or Base contract). Top-line only: consensus score, signal, tracked buyer/seller counts, tracked net USD, canonical status and the safety band — events, holder overlap and coverage detail are capped. Use it to triage whether a token deserves the full cluster_check report.

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": {
      "address": "<address>"
    },
    "name": "cluster_check_lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesToken address: a Solana mint (base58, e.g. Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump) or a Base contract (0x-prefixed, 40 hex chars). Chain is auto-detected from the format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the operation is read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral context by stating it is free, returns top-line fields only, and caps events, holder overlap, and coverage 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 front-loaded with the tool's scope and value, then lists the returned top-line fields and caps in a compact way. Every sentence contributes to helping the agent decide whether to call it.

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 one-parameter read-only report tool with no output schema, the description supplies the key return contents and limitations. Combined with rich annotations and a fully documented parameter schema, it gives the agent enough to call the tool correctly.

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%, and the schema already explains the single address parameter, accepted Solana and Base formats, and automatic chain detection. The description reinforces that it operates on one token but adds no syntax or format meaning beyond the schema.

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?

The description states a specific verb and resource: it produces a lite cluster and consensus report for one token. It distinguishes itself from the sibling full report by explicitly saying it is top-line only and useful for triaging whether a token deserves cluster_check.

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

Usage Guidelines5/5

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

It gives an explicit use case — triage before running the full cluster_check report — and names the alternative tool. The limitation to top-line data and capped detail makes clear when this lite version is appropriate instead of the full report.

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.