Skip to main content
Glama

Veriql token creator history

veriql_deployer

Identify a pump.fun token's creator from its bonding curve and review that creator's other tokens with Veriql verdicts, liquidity withdrawals, and sell-off history.

Instructions

Who created this Solana pump.fun token (read from its bonding curve on chain) and what happened to that creator's other tokens Veriql scored: each one's verdict and any measured liquidity withdrawal or sell-off. History starts 2026-09-30; no record is unknown, never clean.

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": "veriql_deployer"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTokens to list, 1 to 100, default 25
addressYesA pump.fun token mint or a creator wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a fair amount of work: it discloses the data provenance (on-chain bonding curve) and, importantly, the temporal boundary ('History starts 2026-09-30') plus the safety-critical interpretation rule that a missing record means unknown, never clean. That last clause prevents a real misread of empty results. It stops short of disclosing error behavior, latency, or what happens when the address is a creator wallet rather than a mint.

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 compact sentences with the core question front-loaded, followed by the caveat block. Every clause carries information and nothing is padding. The trailing 'no record is unknown, never clean' is telegraphic enough that it takes a re-read, which costs a point on structure.

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 tool with no output schema and no annotations, the description covers the essentials: what is fetched, where it comes from, what the results contain (verdicts, measured withdrawals/sell-offs), and the history horizon. The main residual gap is that it speaks only of 'this Solana pump.fun token' while the schema also accepts a creator wallet, leaving that mode unexplained.

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 both `address` (a pump.fun token mint or creator wallet) and `limit` (1-100, default 25), which sets the baseline at 3. The description adds the useful framing that the address is resolved against an on-chain bonding curve, but it never mentions `limit` or clarifies whether the cap applies to the creator's token history. Net value over the schema is marginal.

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 concretely what the tool returns: the creator of a given pump.fun token, read from its on-chain bonding curve, plus the verdicts and measured liquidity withdrawal/sell-off events for that creator's other scored tokens. That is a distinct resource and scope an agent can separate from veriql_token or veriql_scan. It loses a point because it is framed as a question about outputs rather than a verb+resource statement, and it never names a sibling it is not.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named or contrasted. The closest thing to guidance is the caveat 'no record is unknown, never clean', which tells the agent how to interpret results, not when to select this tool over veriql_token or veriql_batch_screen. Usage is only inferable from the described output.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.