Skip to main content
Glama

Mint Facts

Mint facts (free)

lite_check
Read-onlyIdempotent

Use this when you want a quick free look at a Solana token mint: mint authority, freeze authority, supply and decimals. Rate limited. Facts only, not financial advice. Free, rate limited.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL token mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's incremental value is the rate-limit warning and the fact it returns raw facts with no advisory framing. It does not quantify the rate limit, describe failure/not-found behavior, or say what an invalid mint returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and short, but 'Rate limited' and 'Free, rate limited' appear in consecutive sentences, making the trailing clause pure redundancy that could be one sentence total.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description helpfully names the returned fields, which partly compensates. However, for a token-inspection tool it omits what happens on an unverified or non-mint address and how it differs from check_mint, leaving real gaps in a simple 1-parameter tool's definition.

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?

Only one parameter and schema coverage is 100%, with the schema itself specifying base58 SPL mint address and an example. The description adds no format, validation, or address-resolution nuance beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('quick free look at a Solana token mint') and enumerates the fields returned: mint authority, freeze authority, supply, decimals. An agent knows exactly what it gets. It stops short of the 5 because nothing distinguishes it from the sibling check_mint, which an agent would need to choose between.

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?

Gives a usage trigger ('use this when you want a quick free look') and signals a cost/rate tradeoff, but never states when to prefer check_mint or check_batch instead, nor what 'lite' excludes compared to them. The routing decision between these siblings is left to inference.

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