Skip to main content
Glama

Look up a crypto KOL

kol_lookup
Read-onlyIdempotent

Mihenk's measurement of one X account: Mihenk score (0-10), real reach (typical views per post), followers, region, 90-day call record (share of calls that went the call's way within 24 h) and the last 5 calls.

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

Input Schema

NameRequiredDescriptionDefault
handleYesX handle, e.g. cobie

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-open-world lookup. The description adds valuable return-content context by specifying the Mihenk score, real reach, followers, region, 90-day call record, and last 5 calls, which helps the agent understand what the tool produces.

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 a single dense sentence that front-loads the core purpose and then enumerates the returned metrics with clarifying parentheticals. There is no redundant or wasted wording.

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 simple one-parameter, read-only lookup with no output schema, the description supplies the missing return-value detail by listing every metric the tool returns. Combined with the rich annotations and fully documented parameter schema, it is complete enough for an agent to call 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%, and the single 'handle' parameter is already documented with an example. The description adds no additional parameter-level meaning beyond indicating that the lookup targets one X account, so the baseline 3 is 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 clearly identifies the resource and scope: a measurement of one X account, listing the exact metrics returned. It distinguishes the single-account scope from a basket-like sibling, though it uses the noun 'measurement' rather than an explicit lookup verb.

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 phrase 'one X account' implies this is for single-account lookups, giving some usage context. However, it does not explicitly state when to use this tool versus alternatives or note any exclusions.

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.