Skip to main content
Glama

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

token_verdict

Pre-trade risk verdict on a Base token, $0.01. Give a Base contract address and get: honeypot/transfer-simulation result, buy and sell tax, mint and owner privileges, verified-source status, blacklist and pausable flags, liquidity and holder concentration, scored 0-100 with the explicit red flags named. Aggregated live from honeypot.is, DexScreener, GoPlus and GeckoTerminal. Run it before buying, approving or LP-ing an unknown token.

Input Schema

NameRequiredDescriptionDefault
addressYesBase mainnet token contract address (0x + 40 hex chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / since
      Added value: +{
+  "description": "Optional: the watch.change_token from a previous token_verdict call. When supplied, the response reports only the fields that moved since that snapshot (changed: [{field, from, to}], unchanged: true/false) plus a fresh change_token - so an agent can poll this as a pre-trade gate without diffing.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it names the live sources, the cost ($0.01), the scoring model, and the polling/change_token behavior. It stops short of stating auth needs, rate limits, or latency, but discloses far more than a bare summary.

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?

Front-loaded with the value proposition and cost, followed by deliverables and the call-to-action. It is dense but every clause earns its place by listing return contents an agent needs to interpret the result.

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?

There is no output schema, so the description must describe the return, and it enumerates the fields (simulation result, taxes, privileges, flags, concentration) plus the 0-100 score and named red flags. Nothing an agent needs to invoke or interpret the tool is missing.

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 both 'address' and the optional 'since' param are already fully documented. The description restates 'give a Base contract address' but adds no syntax or format detail beyond what the schema provides, making the baseline 3 correct.

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?

States a specific verb, resource, and scope: a pre-trade risk verdict on a Base token contract. The enumerated deliverables (honeypot simulation, taxes, mint/owner privileges, liquidity) make the purpose unmistakable and clearly distinct from any sibling utility tool.

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

Usage Guidelines4/5

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

Explicitly says when to run it: 'before buying, approving or LP-ing an unknown token,' which is a clear triggering condition. No alternatives or when-not-to-use are named, but no sibling overlaps this function, so the gap is minor.

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

All GadgetHumans API Hub 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