Skip to main content
Glama

fairagent_build_mint_tx

Build an UNSIGNED BNB Chain transaction to mint FairAgent NFTs (bonding curve) or the free claim. Sign and send it with your own wallet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fairagent_build_mint_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNo
refNooptional referrer address
kindNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: the output is unsigned and requires external signing and broadcast. It omits what happens if signing never occurs, whether there is cost, or what the returned payload looks like, leaving meaningful gaps.

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?

Two sentences with zero filler. The unsigned-transaction constraint is front-loaded in the same clause as the purpose, and the follow-up sentence states the required next step.

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

Completeness3/5

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

For a 3-parameter, no-annotation, no-output-schema mutation-adjacent tool, the description covers the transaction lifecycle but not parameter behavior or preconditions. An agent could call it, but would have to guess at qty semantics and how to choose kind.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the description must compensate and largely does not. It hints that 'claim' is free and 'mint' traverses a bonding curve, but says nothing about 'qty' (bounds of 1–20, default when omitted) or about what a referrer address does for 'ref' beyond the schema's own note.

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: 'Build an UNSIGNED BNB Chain transaction' plus the target 'mint FairAgent NFTs (bonding curve) or the free claim.' The parenthetical distinguishes the two operations, and the sibling tools (get_agent, info) are clearly different concerns.

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?

The workflow guidance 'Sign and send it with your own wallet' is explicit and useful, telling the agent this is a prepare-only step. However, there is no guidance on when to pick 'mint' versus 'claim' beyond the enum, and no mention of prerequisites such as price, allowlist, or wallet requirements.

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