Skip to main content
Glama

Mint coin

mint_coin

Mint a signed draft into a live coin. Widget-only: called from the agreement widget's final confirm card. Requires the issuer's Phase wallet address (ph1...) — resolved from the user's existing coins when not supplied.

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": {
      "draftId": "<draftId>"
    },
    "name": "mint_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes
accessTokenNo
widgetTokenNo
issuerAddressNo
idempotencyKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the widget-only invocation path and that the issuer address is resolved from the user's existing coins when omitted, but it never states that minting is irreversible or what permissions/failure modes apply, which matters for a state-changing operation.

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?

Three short sentences with no filler, and the core action is front-loaded ahead of the invocation constraint and the address-resolution rule. Every clause adds information.

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?

This is a mutation tool with no annotations, no output schema, and 0% parameter description coverage, so the description should do more. It leaves three of five parameters and the entire post-mint outcome (what is returned, whether the draft is consumed) unexplained.

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 coverage is 0%, so the description must explain five parameters. It covers issuerAddress well (ph1... format, auto-resolved from existing coins) and implies draftId ('signed draft'), but accessToken, widgetToken, and especially idempotencyKey — a parameter with real retry-safety implications — are completely undocumented anywhere.

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 and resource: 'Mint a signed draft into a live coin,' which is concrete enough to distinguish it from read-oriented siblings like show_agreement or sign_agreement. It never names an alternative tool explicitly, so differentiation relies on inference from the verb.

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?

Gives a clear invocation context ('Widget-only: called from the agreement widget's final confirm card'), which tells the agent this is not a general-purpose entry point. It stops short of naming when-not or the alternative tool that an agent should use outside the widget.

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