Skip to main content
Glama

KOL report for a chain

ecosystem_report
Read-onlyIdempotent

Who among measured KOLs talks about a chain (base, solana, ethereum, bsc, near, arbitrum, hyperliquid, …), its most-discussed tokens, and the KOLs whose posts were followed by more trading volume. Window 7, 30 or 90 days.

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": {
      "chain": "<chain>"
    },
    "name": "ecosystem_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days: 7, 30 or 90
chainYesChain name, e.g. base, solana, ethereum, bsc, near, arbitrum or hyperliquid

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / chain / description
      Added value: +"Chain name, e.g. base, solana, ethereum, bsc, near, arbitrum or hyperliquid"
    • addedInput schema / properties / days / description
      Added value: +"Look-back window in days: 7, 30 or 90"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish a read-only, idempotent, non-destructive, closed-world operation, so the bar is lower. The description adds useful content about what the report covers, but leaves out how 'followed by more trading volume' is measured, data freshness, and result shape.

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?

Two compact sentences front-load the report's contents and end with the time-window options. Nearly every phrase earns its place, with only minor ambiguity in 'posts were followed by more trading volume'.

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 two-parameter read tool with no output schema, the description adequately describes the report's contents and the look-back window. Minor gaps remain around methodology and freshness, but an agent has enough to invoke it 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 description coverage is 100%, so both parameters are already fully documented in the schema. The description restates the 7/30/90-day window and chain examples but adds no extra syntax or semantics beyond the schema, making the baseline 3 appropriate.

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 states a specific resource and angle: a per-chain report on which measured KOLs discuss a chain, its most-discussed tokens, and KOLs whose posts drew trading volume. It is clear what the tool produces, though it does not explicitly name a sibling as an alternative.

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?

Usage is implied by the framing ('Who among measured KOLs talks about a chain...'), making the intended analysis obvious. However, it gives no explicit when-to-use conditions, prerequisites, or comparison to siblings such as kol_basket or organic_interest.

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.