Skip to main content
Glama

airdrop score

airdrop-score
Read-onlyIdempotent

Airdrop eligibility score for an address + calibrated expected value of the opportunity (sybil-rejection and token-decay adjusted) Price: $0.05 per call, USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "airdrop-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNooptional: base (default)|ethereum|optimism|arbitrum|gnosis
addressNo0x... (optional)
expected_payout_usdNonumber (optional, default 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"base|ethereum|..."New value: +"optional: base (default)|ethereum|optimism|arbitrum|gnosis"
    • changedInput schema / required
      Previous value: -[
      -  "chain"
      -]New value: +[]
  2. First observed

TDQS

B3.2/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 is covered elsewhere. The description's real contribution is the payment model — $0.05 per call, USDC on Base via x402 — which is meaningful behavioral context an agent needs before invoking. Beyond that it adds little: no rate limits, no failure modes, and no note on what happens when address is omitted despite all parameters being optional.

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 tight sentences with the core purpose front-loaded and the cost constraint appended where it is easy to find. Minor flaws: the price clause runs into the previous sentence without separation, and the parenthetical adjustment list is dense, but nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return semantics, and it does so only roughly — an 'eligibility score' and an 'expected value' with no indication of format, range, or confidence. A notable gap is that all three parameters are optional and the description never says what a call with no address or chain returns.

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%, so every parameter including chain enum values and the expected_payout_usd default of 200 is already documented in the schema. The description adds conceptual framing (sybil-rejection and token-decay adjustment) but never explains how expected_payout_usd actually influences the returned score, so it does not exceed the schema baseline.

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 names a specific output artifact: an airdrop eligibility score for an address plus a calibrated expected-value estimate of the opportunity, with two named adjustments (sybil rejection, token decay). That is far more than a restatement of the name 'airdrop-score'. It does not contrast itself with any sibling, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisite statement, and no alternative suggested for cheaper or related checks. The pricing sentence tells the agent what a call costs but not when the call is warranted over alternatives.

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.

Resources