Skip to main content
Glama

complete_merchant_enrollment_transaction

Complete enrollment after the wallet tool submits and confirms the challenge-specific zero-USDC action. Accepts the transaction hash; never accepts or needs a private key. Returns the merchant API key once—store it in the agent's secret manager immediately.

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": {
      "wallet": "<wallet>",
      "name": "<name>",
      "challengeId": "<challengeId>",
      "method": "<method>",
      "transactionHash": "<transactionHash>"
    },
    "name": "complete_merchant_enrollment_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
methodYes
walletYes
challengeIdYes
transactionHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.4/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 behavioral burden, and it does disclose two important traits: no private key is accepted or needed, and the merchant API key is returned exactly once and should be stored immediately. It does not state idempotency (what happens if the call is retried with the same hash), whether the key is unrecoverable after a lost response, or what errors look like when the challenge is unconfirmed.

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?

Three short sentences, front-loaded with the triggering condition, then the security constraint, then the output handling instruction. No filler; the only reason it is not a 5 is that the output-warning sentence could be tightened slightly.

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?

The tool has five required parameters, no annotations, and no output schema, which raises the bar. The description covers the key return value and the security posture well, but leaves four of five parameters undocumented, which is a meaningful gap for a state-mutating enrollment tool.

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 0% across five required parameters (wallet, name, challengeId, method, transactionHash), so the description must compensate. It only explains transactionHash, leaving wallet, name, challengeId, and the method enum (approve_zero vs transfer_zero) entirely to bare JSON patterns and enum values with no stated meaning or selection criteria.

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 states a specific verb and resource ('Complete enrollment') and pins the precondition to a concrete upstream action ('after the wallet tool submits and confirms the challenge-specific zero-USDC action'). It implicitly separates itself from the signature-based sibling by requiring a transaction hash, but never names that alternative, so an agent must infer the distinction from the parameter name alone.

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?

The prerequisite is explicit: call this only after the wallet tool has submitted and confirmed the zero-USDC action. That is real sequencing guidance. There is no explicit when-not condition and no named alternative (e.g., complete_merchant_enrollment_signature) for the case where a signature rather than a transaction hash is produced.

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