Skip to main content
Glama
Sign In

Tlacuilo

by app.vercel.tlacuilo-jet
OverviewDiscussionsAdmin

token_verdict

token_verdict
Read-only

Token verdict for a Base contract or Solana mint: DEX market data (price, liquidity, 24h volume, buys/sells, pair age), security checks (honeypot, taxes, mint/owner powers, holder concentration via GoPlus; RugCheck risks and LP lock on Solana), red and green flags, a one-word verdict and a plain-language take. Entertainment, not trading advice. Price: $0.02 USDC per call (x402).

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

Input Schema

NameRequiredDescriptionDefault
chainNobase or solana (default base)
addressYesToken contract (Base) or mint address (Solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotation, the description adds crucial behavioral traits such as the specific pricing ($0.02 per call) and details the exact outputs like 'a one-word verdict' and 'a plain-language take.'

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 information is logically segmented: domain, data points, disclaimers, and cost. Every sentence contributes high-value context without being repetitive.

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?

Given the complexity of token security, the definition is complete, explaining exactly what inputs are needed and what types of comprehensive outputs a user can expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description effectively clarifies the ambiguity of the 'address' parameter by specifying that it must be a 'Token contract (Base) or mint address (Solana),' tying the expected address format to the selected chain context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is highly specific, clearly defining the tool's function as providing token verdicts by assessing DEX market data and security features like GoPlus and RugCheck.

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

Usage Guidelines5/5

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

The definition provides robust usage context by stating that it is for 'Entertainment, not trading advice,' which is essential guidance to prevent misuse as a financial advisory tool.

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

All Tlacuilo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources