Skip to main content
Glama

Coins a KOL promoted lately

kol_basket
Read-onlyIdempotent

The spot coins a KOL promoted in the last 7, 30 or 90 days, with the median 24 h move after their posts. Not a recommendation; it shows what the KOL promoted and what followed.

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": {
      "handle": "<handle>"
    },
    "name": "kol_basket"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days: 7, 30 or 90
handleYesX handle of the KOL without @, e.g. cobie

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Look-back window in days: 7, 30 or 90"
    • addedInput schema / properties / handle / description
      Added value: +"X handle of the KOL without @, e.g. cobie"
  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 declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile needs no restating. The description adds genuinely useful behavior beyond that: the payload reports a median 24h post-call move and is explicitly non-advisory. It leaves out how many coins come back, what happens with an unknown or inactive handle, and any rate/coverage limits.

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 sentences, front-loaded with the core capability and followed by the interpretive caveat; nothing is padded. Minor cost: the opening "The spot coins..." is compressed jargon that takes a beat to parse.

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?

With no output schema, the description carries the burden of explaining returns, and it does name the key field (median 24h move) alongside the coin list. For a two-parameter read-only tool that is largely sufficient, though result count and handling of a handle with no promos remain unstated.

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%, with both handle ("X handle of the KOL without @, e.g. cobie") and the days enum already documented in the schema. The description repeats the 7/30/90 window but adds no new semantics such as whether the window is measured from post time or how days interacts with the 24h move metric; baseline 3 applies.

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 spot coins a KOL promoted in the last 7, 30 or 90 days, with the median 24 h move after their posts" names the resource (coins promoted by a KOL) and the metric returned (median 24h move), which is specific enough to distinguish it from lookups or reports. It stops short of naming a sibling such as kol_lookup to delineate where this ends and that begins.

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?

The clause "Not a recommendation; it shows what the KOL promoted and what followed" frames how to interpret results, implying the tool is for descriptive inspection of a KOL's track record rather than screening/due diligence. There is no explicit when-to-use versus kol_lookup or ecosystem_report, and no stated prerequisites (e.g. handle must exist on X).

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.