Skip to main content
Glama

Veriql launch-safety score

veriql_launch

Generate a transparent 0-100 launch-safety score for a token or mint, with itemised penalty drivers and full metrics across EVM, Tron, and Solana.

Instructions

A transparent 0-100 launch-safety score for a token/mint with itemised penalty drivers and full metrics. EVM chains + Tron + Solana.

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

Input Schema

NameRequiredDescriptionDefault
addressYesToken contract / mint address
chainIdNoChain id or key (e.g. 1, base, solana); defaults to Ethereum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return shape (a score plus itemised penalty drivers and metrics) and the supported chain families (EVM, Tron, Solana), but says nothing about cost, rate limits, authentication, or whether the assessment is deterministic.

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 purpose front-loaded and no filler. The second sentence is a fragment, but it carries useful scope information.

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?

The tool is simple (one required parameter, no output schema) and the description covers purpose, output components, and chain coverage. However, without an output schema, the description should say more about the structure of the returned metrics and penalty drivers than a single clause.

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 both parameters are already documented in the schema. The description's chain coverage sentence is only lightly additive beyond the chainId field, and it adds no syntax or format detail for address.

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 resource and output: a 0-100 launch-safety score for a token/mint, with itemised penalty drivers and metrics. That is clearly distinct from batch screening or raw scanning, though it never explicitly contrasts itself with siblings like veriql_scan or veriql_preflight.

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?

Usage is only implied by the phrase 'launch-safety score' and the token/mint subject, which suggests pre-launch due diligence. There is no explicit when-to-use statement, no exclusion of alternatives such as veriql_preflight or veriql_token, and no prerequisites.

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