Skip to main content
Glama

Mint Facts

Mint facts, batch

check_batch
Read-onlyIdempotent

Use this when you need the /check facts for up to 10 Solana token mints in one call (comma-separated mints). All-or-nothing: if any mint fails you are not charged. Facts only, not financial advice. Price: $0.08 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": {
      "mints": "<mints>"
    },
    "name": "check_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintsYes1 to 10 Solana mint addresses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the all-or-nothing billing rule ('if any mint fails you are not charged'), the exact price ($0.08 USDC per call), the payment network (x402, eip155:8453), and the precise payment handshake via _meta["x402/payment"] after the first call. These are operational facts an agent cannot infer from annotations or schema and materially change how it should call the tool.

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 when-to-use clause and the batch limit are front-loaded, followed by the billing and payment mechanics an agent needs before invoking it. 'Facts only, not financial advice' is a disclaimer that consumes space without helping tool selection, but the rest of the text is dense and purposeful.

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 one-parameter batch tool with a paid x402 flow, the definition covers the batch limit, partial-failure billing, price, and payment attachment mechanics — the parts most likely to cause a failed call. With no output schema, it would be stronger if it sketched the shape of the returned facts, but nothing critical to correct invocation 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 coverage is 100% and the schema already documents the 1–10 mint array, so the baseline is 3. The description adds that the mints are Solana addresses, but its '(comma-separated mints)' phrasing is in mild tension with the array-typed parameter and could mislead an agent about the expected encoding.

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 resource (the /check facts) and a clear batching scope (up to 10 Solana token mints in one call), which lets an agent distinguish it from single-mint siblings such as check_mint. The term 'facts' is left unexpanded, so what the tool actually returns is only loosely characterized, but the verb+resource+scope combination is clear.

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 the /check facts for up to 10 ... in one call' gives an explicit triggering condition tied to batch size. It never names a single-mint alternative or states when not to use batching, so the guidance is clear but not fully exclusionary.

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