ashfields-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mint_infoA | Returns current Ashfields mint status: price per token, total minted so far, remaining supply, whether minting is currently active, and contract addresses. Call this first to confirm minting is open before attempting a mint. |
| check_walletA | Returns the configured wallet address, its $ASH token balance, its current $ASH allowance for the Ashfields contract, and its ETH balance for gas. Also reports the maximum number of tokens it can mint right now. |
| approve_ashA | Approves the Ashfields contract to spend $ASH tokens from the configured wallet. Submits the approval transaction and waits for on-chain confirmation. Required before minting if the current allowance is insufficient. |
| mint_ashfieldA | Mints one or more Ashfields NFTs. Automatically approves $ASH if the current allowance is insufficient, then submits the mint transaction and waits for confirmation. Returns the minted token IDs and OpenSea links. Burns 100,000 $ASH per token permanently (sent to 0xdead). |
| trigger_distributeA | Calls distribute() on the RoyaltyDistributor contract. Permissionless — any wallet can trigger this at any time. Splits accumulated royalty ETH: 1% to creator, 1% to $ASH team, 8% buys $ASH on Uniswap and burns it to 0xdead. Requires at least 0.005 ETH in the distributor to execute. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action: reading mint status, checking wallet state, approving spending, minting, and triggering distribution. The only slight overlap is approve_ash versus mint_ashfield's auto-approve, but both are clearly differentiated by purpose.
All tool names follow a verb_noun pattern and use snake_case consistently. Minor inconsistency exists between get_mint_info and check_wallet, both of which are informational but use different verbs; overall the pattern is predictable.
Five tools is well-scoped for a focused NFT minting and royalty distribution server. Each tool maps to an essential step in the workflow without unnecessary bloat.
The core minting flow is fully covered: check status, inspect wallet, approve, mint, and distribute royalties. A minor gap is the lack of a dedicated way to query the RoyaltyDistributor's balance or distribution status, which would require external verification.