Skip to main content
Glama

complete_merchant_credential_rotation_transaction

Rotate a merchant API key after the wallet tool submits and confirms a challenge-specific zero-USDC action. Returns the replacement key once and invalidates the old one. Store the new key 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>",
      "challengeId": "<challengeId>",
      "method": "<method>",
      "transactionHash": "<transactionHash>"
    },
    "name": "complete_merchant_credential_rotation_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantial work: it discloses that the old key is invalidated (an irreversible mutation), that the replacement key is returned exactly once, and that it must be stored immediately. That is exactly the kind of consequence an agent needs before calling. It omits auth/ownership requirements and failure modes, so not a 5.

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 sentences, front-loaded with the action, then outcome, then the operational directive. Every sentence carries information and nothing is padding. Minor cost is that the first sentence packs the precondition into a dense clause, but it is still readable on one pass.

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 four-required-parameter mutation tool with no annotations and no output schema, the description covers the return contract (one-time replacement key) and the key-invalidation side effect, which substitutes for a missing output schema. It leaves the enum parameter and challenge/transaction linkage undocumented, which is a real gap for a tool that will fail if those are supplied incorrectly.

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 four required parameters, so the description must compensate and largely does not. 'Challenge-specific' loosely hints at challengeId and the wallet/transactionHash link is implied by 'the wallet tool submits and confirms', but the method enum (approve_zero vs transfer_zero) is never explained and there is no statement of which value to pick or how transactionHash is obtained.

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 (rotate a merchant API key) plus the precondition (wallet tool submitted and confirmed a challenge-specific zero-USDC action) and the outcome (returns replacement key, invalidates old). An agent can identify what this does without opening the schema. It stops short of distinguishing itself from the sibling complete_merchant_credential_rotation_signature, which is presumably the alternate authorization path.

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?

Gives an implicit sequencing requirement — call this only after the wallet tool submits and confirms the challenge action — which tells an agent where in the flow it sits. However, it never names an alternative path (the signature-based sibling or the challenge-creation step) or states when NOT to use it, leaving the choice between transaction and signature completion to inference from the required transactionHash parameter.

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