Skip to main content
Glama

CON, Central Operating Network

Check a Solana coin

check_coin
Read-only

CON's public coin check for one Solana token (mint address): risk class, the dev wallet's earlier coins and exits, wallet rings, holder concentration, contract rights and findings, read against CON's record of every Solana launch since Oct 2026. Same data as centralonet.com/scan, no account.

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": {
      "mint": "<mint>"
    },
    "name": "check_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58, 32 to 44 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context beyond them: the data source is CON's record of every Solana launch since Oct 2026, which implies a coverage window, and that no account is needed. It stops short of describing freshness, latency, or failure behavior for a mint outside that window.

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?

A single front-loaded sentence with the scope stated first and the risk dimensions enumerated after. The list of data categories is dense but each item conveys what the agent will get back, so the length is largely earned.

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 read-only, one-parameter lookup with no output schema, the description is sufficient: it tells the agent what input to supply, that no account is required, and roughly what the result covers. The main remaining gap is the Oct 2026 data-window implication for older tokens, which is hinted at but not spelled out.

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 100% and the single parameter is documented as a base58 mint address with a length range, so the schema does the heavy lifting. The description reinforces the 'one token' scope, making clear the argument is a mint address rather than a symbol or name, which is a small but genuine clarification.

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 verb+resource ('public coin check for one Solana token (mint address)') and enumerates the returned risk dimensions (risk class, dev wallet history, wallet rings, holder concentration, contract rights). It is clearly a per-token risk lookup, distinct in kind from the sibling names like define_term and launch_index, though it never explicitly contrasts itself with them.

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 implied rather than stated: it is the tool for vetting a single token, and the 'no account' note tells the agent it can call this without auth. There is no explicit when-not guidance or named alternative for batch/index-style questions, which the sibling launch_index might cover.

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.

Resources