Skip to main content
Glama
Sign In
@quackai/q402-mcp

@quackai/q402-mcp

Official
by quackai-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

q402_escrow_lock

Fund a pending escrow by gaslessly locking buyer funds into the vault using EIP-7702. Server signs for agent wallets to eliminate local key handling; always confirm escrow details first.

Instructions

Fund a pending escrow: the BUYER gaslessly locks the amount into the vault via EIP-7702 (Q402 relays + sponsors gas). MOVES REAL FUNDS. If the escrow is funded by an Agent Wallet (created with walletId), the server signs it for you - no local key needed. Otherwise requires Q402_PRIVATE_KEY = the buyer's key. ALWAYS confirm the exact amount/seller/chain with the user before calling (confirm:true).

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": {
      "escrowId": "<escrowId>",
      "confirm": "<confirm>"
    },
    "name": "q402_escrow_lock"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMUST be true, only after the user explicitly confirmed this exact escrow action in chat.
escrowIdYesThe esc_... id from escrow_create.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.14

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries full burden and excels: it warns 'MOVES REAL FUNDS', explains gasless sponsorship via EIP-7702, details key requirements (server signs for Agent Wallet, otherwise Q402_PRIVATE_KEY), and mandates user confirmation. This is exceptionally transparent for a financial mutation tool.

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?

The description is a bit long but front-loaded with purpose and every sentence contributes critical information (mechanism, real funds, key requirements, confirmation). The use of caps and clear segmentation helps scanning, though it could be slightly tightened.

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

Completeness4/5

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

Given the moderate complexity (funding escrow with gasless flow) and lack of output schema, the description covers purpose, mechanism, prerequisites, and mandatory confirmation. It doesn't state return values, but that's not essential here; overall it's sufficiently complete for an agent to invoke correctly.

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

Parameters4/5

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

Schema coverage is 100% and already describes both params. The description adds value by explaining that escrowId comes from escrow_create and clarifying that confirm:true must only be set after explicit user confirmation of the exact action, reinforcing the safety intent.

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?

The description states a clear, specific verb ('Fund') and resource ('pending escrow'), plus the mechanism ('gaslessly locks the amount into the vault via EIP-7702'). It distinguishes from sibling escrow tools like release, refund, and dispute by focusing on the funding step.

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 implies when to use this tool (after escrow_create, before release/refund) and provides an explicit safety rule: 'ALWAYS confirm the exact amount/seller/chain with the user before calling (confirm:true)'. It doesn't explicitly mention alternatives, but the sibling names make that clear.

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

Deploy Server

Other Tools