Skip to main content
Glama

Organic KOL interest in a token

organic_interest
Read-onlyIdempotent

Which measured KOLs talked about a token, how many views those posts got and how much was organic (posts that 3+ accounts published with the same text count as coordinated). 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": {
      "token": "<token>"
    },
    "name": "organic_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days: 7, 30 or 90
tokenYesTicker without $ (e.g. PEPE) or a contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / days / description
      Added value: +"Look-back window in days: 7, 30 or 90"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds valuable context beyond that: it explains the organic metric definition (3+ accounts posting identical text counts as coordinated) and the supported look-back windows, which is important for interpreting results.

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?

The definition is front-loaded and dense, with no wasted sentences. The parenthetical definition of coordinated posts is slightly disruptive but earns its place by clarifying the key metric.

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-only tool with no output schema, the description explains what is returned (KOLs, views, organic share) and how organicness is defined. It is complete enough to call correctly, though return-shape details like result limits or pagination are absent.

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 the schema already documents the token format (ticker without $ or contract address) and the 7/30/90-day enum with a 30-day default. The description restates the window options but adds no format or edge-case detail beyond the schema.

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 analysis (which KOLs posted about a token, view counts, organic share) and the token/window scope. It is clear and unlikely to be confused with lookups or reports, but it never names or distinguishes any sibling tool explicitly.

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 description: use it to measure organic KOL interest for a token. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the context.

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.