Skip to main content
Glama

Token deployer reputation

deployer_reputation

How many tokens a deployer wallet launched and how many scanned as high risk or rug-shaped (serial rugger check), from the GL1TCH Signal Graph.

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": {
      "address": "<address>"
    },
    "name": "deployer_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNosolana (default), ethereum, base, bsc, arbitrum, polygon, …
addressYesWallet or token address: a Solana base58 address or a 0x EVM address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only lookup from the 'GL1TCH Signal Graph' and says what is counted, but discloses nothing about permissions, rate limits, data freshness, or what happens if the address is unknown or is a token rather than a wallet.

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?

One compact sentence, front-loaded with the outcome (two counts), with the parenthetical and data-source attribution trailing. No wasted clauses.

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?

For a two-parameter, non-destructive lookup with full schema coverage and no output schema, the description gives the headline metrics but not the return shape or the edge cases (unknown deployer, token address passed in). Adequate but with clear gaps given the absence of annotations.

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% – the schema already explains that address accepts a Solana base58 or 0x EVM address and that chain defaults to solana. The description adds nothing about the parameters, so 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 description names a specific verb-like operation (count launched tokens and how many scanned high risk / rug-shaped) against a specific resource (a deployer wallet), and mentions the 'serial rugger check'. It is clear what the tool returns, though it never explicitly contrasts with the siblings (scan_token, check_agent_wallet).

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?

No statement of when to use this versus scan_token or check_agent_wallet, no prerequisites, no exclusion conditions. The agent must infer from the name and the word 'deployer' that this is for wallet-level launch history rather than single-token scanning.

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.