Skip to main content
Glama

open_escrow_job

[Private] Buying from another agent? Lock the payment in escrow so the seller only gets paid if the delivery passes the audit. Example: storeId='dataforge-ai', tokenSymbol='USDC', tokenAmount=10.

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": {
      "storeId": "<storeId>",
      "tokenSymbol": "<tokenSymbol>",
      "tokenAmount": "<tokenAmount>"
    },
    "name": "open_escrow_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerIdNoBuyer agent identifier opening the escrow order.
minRowsNoMinimum dataset rows required for settlement.
storeIdYesTarget verified store identifier.
tokenAmountYesToken amount to fund into escrow.
tokenSymbolYesPayment token symbol.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / buyerId / description
      Added value: +"Buyer agent identifier opening the escrow order."
    • addedInput schema / properties / minRows / description
      Added value: +"Minimum dataset rows required for settlement."
    • addedInput schema / properties / storeId / description
      Added value: +"Target verified store identifier."
    • addedInput schema / properties / storeId / examples
      Added value: +[
      +  "dataforge-ai"
      +]
    • addedInput schema / properties / tokenAmount / description
      Added value: +"Token amount to fund into escrow."
    • addedInput schema / properties / tokenSymbol / description
      Added value: +"Payment token symbol."
    • addedInput schema / properties / tokenSymbol / enum
      Added value: +[
      +  "USDC",
      +  "ETH",
      +  "SOL",
      +  "VIRTUAL",
      +  "USDT"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so safety is largely covered. The description adds genuinely new behavior: funds are locked and the seller is paid only if delivery passes the audit. It omits what happens if the audit fails, whether a refund path exists, and the risk of duplicate orders implied by idempotentHint=false.

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?

Two short sentences, front-loaded with the core action and the settlement condition. The leading "[Private]" marker is unexplained jargon that consumes space without informing an agent, but overall the text is tight.

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 5-parameter state-changing tool with no output schema, the description covers the purpose and the payout condition but not the return value (presumably an escrow order reference needed by the audit/claim siblings) or failure handling. Adequate but with clear gaps for a financial mutation.

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 description coverage is 100%, so every parameter including buyerId and minRows is already documented, setting the baseline at 3. The worked example restates storeId/tokenSymbol/tokenAmount values already present as schema examples and adds no interpretation of minRows' effect on settlement.

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: lock a payment in escrow, with the conditional settlement rule spelled out. An agent can tell this is the escrow-opening action rather than the audit_* verification or refund siblings, though no sibling is named explicitly.

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?

The opening question "Buying from another agent?" gives a usable trigger condition, which implies when to use it. However, there is no guidance on when not to use it, no mention of prerequisites (e.g. a verified store from discover_verified_stores), and no routing versus alternatives like purchase_firstparty_catalog_item or the timeout-refund sibling.

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.