Skip to main content
Glama
XCP
by XCP

compose_fairminter

Compose a transaction to launch a new asset with fair minting, defining price, supply caps, mint limits, and block schedule.

Instructions

Compose a transaction to create a fair minting launch for a new asset. For XCP-420 compliant launches, use compose_xcp420_fairminter instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetYesAsset name to create
priceNoRaw integer price per mint in the payment asset (XCP). For XCP: human amount * 10^8 (e.g. 0.1 XCP = 10000000).
addressYesSource Bitcoin address
hard_capNoRaw integer max total supply. For divisible: human amount * 10^8.
soft_capNoRaw integer soft cap. For divisible: human amount * 10^8.
divisibleNoWhether the asset is divisible (8 decimal places)
end_blockNoBlock height when minting ends
mime_typeNoMIME type for inscription (e.g. image/png, text/plain)
inputs_setNoComma-separated UTXOs to use as inputs (txid:vout)
descriptionNoAsset description
inscriptionNoBase64-encoded inscription data (requires P2TR address)
start_blockNoBlock height when minting starts
burn_paymentNoWhether payment is burned (true) or sent to issuer (false)
lock_quantityNoLock supply so no further issuance is possible
sat_per_vbyteNoFee rate in satoshis per virtual byte (e.g. 1, 5.5, 0.15). Check get_fee_estimate for current market rates.
max_mint_per_txNoRaw integer max per tx. For divisible: human amount * 10^8.
premint_quantityNoRaw integer amount to premint to issuer. For divisible: human amount * 10^8.
quantity_by_priceNoRaw integer tokens received per price payment. For divisible: human amount * 10^8.
max_mint_per_addressNoRaw integer max per address. For divisible: human amount * 10^8.
minted_asset_commissionNoCommission fraction (0-1) on minted assets
soft_cap_deadline_blockNoDeadline block for reaching soft cap. Must be less than end_block.
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description adds 'compose a transaction' implying a non-read-only operation. It does not disclose what the tool returns, whether broadcasting is required, or other behavioral nuances, so it adds limited value beyond annotations.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the action and resource, and includes a useful pointer to an alternative. Every word earns its place.

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

Completeness2/5

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

With 21 parameters, no output schema, and no explanation of what a fairminter launch entails or what the returned transaction looks like, the description is too sparse. It also fails to clarify the relationship with compose_fairmint, leaving a significant completeness gap.

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 description coverage is 100%, so the schema fully documents parameters. The description itself offers no additional parameter guidance, staying at the baseline for high schema coverage.

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 clearly states the tool composes a transaction to create a fair minting launch for a new asset. It distinguishes from compose_xcp420_fairminter, but does not differentiate from the similarly named sibling compose_fairmint, leaving potential confusion.

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?

It explicitly names an alternative for XCP-420 compliant launches, providing a clear when-not-to-use condition. However, it does not address the closely related compose_fairmint sibling or other compose_* alternatives, leaving some usage context implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/XCP/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server