Skip to main content
Glama

solana_mint_auditor

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

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the audit surface (authorities, supply, decimals, Token-2022 extensions, holder concentration), which implies a read-only analysis, but it never states that it is non-mutating, whether it makes network calls, how it behaves for non-Token-2022 mints, or what happens on an invalid/uninitialized mint.

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 that names the target first and then lists the inspected facets; there is no filler. It is dense but readable, with only a minor cost in that the enumerated list reads like a feature dump rather than a sentence.

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, the enumerated audit facets effectively communicate what the caller gets back, which is the key missing piece for a single-parameter inspection tool. Only failure modes and the read-only guarantee are left unstated.

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 exists and schema coverage is 100%, so the schema already documents 'Solana mint address'. The description adds nothing about address format, whether the mint must be an existing on-chain account, or validation expectations, so the baseline of 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 ('Audit') and resource ('Solana SPL mint') and enumerates exactly what is inspected: mint/freeze authority, supply, decimals, Token-2022 extensions, top-holder concentration. The chain/token-standard specificity implicitly separates it from base_erc20_inspector, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as token_safety_composite or base_erc20_inspector. An agent must infer that this is the Solana-mint-specific inspection path purely from the noun phrase.

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