Skip to main content
Glama

Mint Facts

Mint facts (full)

check_mint
Read-onlyIdempotent

Use this when you need on-chain facts about a Solana SPL token mint before interacting with it: mint and freeze authority, supply, decimals, Token-2022 extensions (transfer fee, permanent delegate, transfer hook...) and factual flags. Facts only, no verdict. Automated facts, not financial advice. Price: $0.02 USDC per call (x402, eip155:8453); pay by attaching an x402 payment in _meta["x402/payment"] after the first call 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": {
      "mint": "<mint>"
    },
    "name": "check_mint"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL token mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), and the description adds real value beyond them: the $0.02 x402 payment cost and the two-step handshake where the first call returns payment requirements before a payment is attached in _meta. It also states 'facts only, no verdict,' clarifying no scoring is produced. It does not describe error behavior or rate limits.

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 usage trigger is front-loaded, followed by the fact list and then the payment mechanics, which is a sensible order. The 'Automated facts, not financial advice' line is somewhat boilerplate but earns a small place given the financial-data context.

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 single-parameter read tool with rich annotations but no output schema, the description enumerates the returned fields well enough for an agent to know what it will get, and explains the payment flow. Only minor items like failure modes are absent.

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?

With one parameter at 100% schema description coverage (base58 Solana mint address plus an example), the schema carries the burden. The description only restates that the input is a Solana SPL token mint, adding no format or validation detail beyond the schema.

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 states a specific verb and resource ('on-chain facts about a Solana SPL token mint') and enumerates exactly which facts are returned: mint/freeze authority, supply, decimals, Token-2022 extensions, and factual flags. It does not distinguish itself from siblings like lite_check or check_batch, so it falls short of a 5.

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?

'Use this when you need on-chain facts ... before interacting with it' gives a clear triggering condition. There are no explicit exclusions or pointers to cheaper alternatives (e.g. lite_check) despite a $0.02 per-call cost, which is the main gap.

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