Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_solana_mint_auditor

Audit a Solana SPL mint for mint/freeze authority status, supply, decimals, Token-2022 extensions, and top-holder concentration.

Instructions

[On-Chain Intelligence] Audit a Solana SPL mint: mint/freeze authority, supply, decimals, Token-2022 extensions and top-holder concentration Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description must carry the behavioral burden; it usefully discloses the scope of returned data plus measured p50/p95 latency and the backing endpoint. It does not state that the operation is read-only (only implied by 'Audit'), nor does it cover authentication, rate limits, or what happens with a malformed or non-existent mint address.

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 audited fields are front-loaded in a single dense sentence, so the core value lands immediately. The trailing benchmark and endpoint sentences are lower-value boilerplate but short and do not obscure the purpose.

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?

With no output schema and no annotations, the description compensates well by naming the specific data points returned (authorities, supply, decimals, extensions, holder concentration). Only the failure/empty-result behavior is unaddressed, which is a minor gap for a single-parameter read tool.

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 ('mint') exists and schema description coverage is 100%, so the schema already defines it as a Solana mint address. The description adds no format, encoding, or validation detail beyond that baseline.

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 ('Audit a Solana SPL mint') and enumerates exactly what is inspected: mint/freeze authority, supply, decimals, Token-2022 extensions, and top-holder concentration. That level of detail separates it from siblings like caelara_crypto_base_erc20_inspector (a different chain standard) and caelara_crypto_token_safety_composite without requiring the schema to be opened.

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 by the purpose: pass a mint address when you need on-chain mint metadata and holder concentration. There is no explicit statement of when to prefer this over caelara_crypto_token_safety_composite or caelara_crypto_dex_liquidity_depth, and no prerequisites or exclusions are given, so guidance is adequate but inferential.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools