Skip to main content
Glama

Due-diligence check of a crypto project's website before you buy or interact

crypto_site_check
Read-only

Due-diligence check of a crypto project's website before you buy or interact: domain age (RDAP) and first archive date, HTTPS/security, socials (X, Telegram, Discord, GitHub), docs/whitepaper, team page, audit firms mentioned, contract addresses on the page (optionally verifies yours), scam phrases and wallet-drainer signals (seed-phrase inputs), template/free-hosting signs. Returns a 0-100 trust score, red and green flags. Heuristics, not financial advice. Takes 3-8 s. Price: $0.02 per call (x402, USDC on Base). Without payment, returns the payment requirements.

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": {
      "url": "<url>"
    },
    "name": "crypto_site_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesProject website (public http(s) URL)
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.
contractNoOptional token contract address to verify it is published on the site

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly and openWorld; the description adds the things an agent actually needs: latency (3-8 s), cost ($0.02 per call, x402 USDC on Base), and the fact that an unpaid call returns payment requirements rather than a result. It also discloses output shape (0-100 trust score, red/green flags) and sets expectations that results are heuristics, not financial advice.

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?

The purpose is front-loaded in the first clause and the operational facts (time, price, unpaid behavior, disclaimer) are packed into trailing sentences with no filler. The middle section is a dense comma list of checked signals, which is information-rich but slightly run-on; a reader must parse it rather than skim.

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?

With no output schema, the description carries return-value disclosure itself and does so (trust score range, red/green flags, payment requirements on unpaid calls). Combined with latency, pricing, and the disclaimer, an agent has everything needed to decide, sequence, and interpret a call without opening anything else.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds meaning: the `contract` parameter is framed as 'contract addresses on the page (optionally verifies yours)', clarifying it is a verification target rather than a lookup key. It also reinforces the two-phase payment flow in prose, which helps an agent sequence calls correctly even if the schema already hints at it.

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 and resource ('due-diligence check of a crypto project's website') and enumerates exactly what is inspected: RDAP domain age, archive date, HTTPS, socials, docs, team page, audits, contract addresses, scam/drainer signals, template hosting. The scope is clearly broader than a single-purpose sibling like https_check or domain_whois, so an agent can tell what it is buying.

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?

The title and opening clause give explicit timing context ('before you buy or interact'), which tells the agent the decision point this tool serves. It stops short of naming when-not to use it or pointing to narrower alternatives (https_check, domain_whois) for a single-signal check, so it is a strong 4 rather than a 5.

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.