Skip to main content
Glama

Hominoport

Submit the escrow authorisation

submit_escrow_signature

After request_action with payment_flow escrow: submits your EIP-712 signature of typed_data (ReceiveWithAuthorization). This grants the escrow's collector the authority to pull the stated USDC amount when the provider authorizes; no transfer happens on submission. If the provider does not authorize before the stated time the authorisation lapses; after the task deadline you can reclaim on-chain yourself (that call needs a little ETH on Base for gas).

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": {
      "task_id": "<task_id>",
      "signature": "<signature>"
    },
    "name": "submit_escrow_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
signatureYes0x-prefixed hex, 65 bytes or an ERC-6492 wrapper

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the key behavioral effects: no transfer occurs on submission, the signature grants the escrow's collector authority to pull USDC once the provider authorizes, the authorization lapses if the provider does not act, and the user can later reclaim on-chain with ETH for gas. These details meaningfully clarify the non-destructive but consequential nature of the call.

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?

The definition is front-loaded with the prerequisite condition and then explains the effect, lapse behavior, and reclaim path without filler. Every sentence contributes operational context.

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?

For a mutation-style submission tool with no output schema, the description covers the important behavioral and follow-up context. It leaves minor gaps around the response shape and the exact meaning of task_id, but an agent has enough information to invoke it correctly.

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

Parameters3/5

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

Schema coverage is 50%, and the description adds useful meaning for the signature parameter by identifying it as an EIP-712 typed_data signature for ReceiveWithAuthorization. However, it does not clarify the task_id parameter or explain how it relates to the escrow task beyond the schema's type.

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 names a specific action, submit_escrow_signature, and precisely describes the resource as an EIP-712 signature of typed_data for ReceiveWithAuthorization. It also distinguishes the operation from a transfer by explaining that this grants authority rather than moving funds.

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 clearly states the triggering condition: use after request_action with payment_flow escrow. It also explains what happens if the provider does not authorize and when the user can reclaim on-chain, giving strong contextual guidance, though it does not explicitly compare against sibling alternatives.

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