Skip to main content
Glama

record_virtuals_tender_funding_v2

Destructive

Record canonical Base transaction hashes for an existing ACP V2 tender funding reservation after the customer wallet submits it; this action cannot submit a transaction.

Instructions

[Capability: available_when_deployment_prerequisites_are_met; tier: x402_or_subscription_with_authenticated_session; API: /api/v1/agent/virtuals-acp; authority: /api/v1/agent/status] Durably record canonical Base transaction hashes after the customer wallet submits an existing ACP V2 funding reservation. This action cannot submit a transaction itself.

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": {
      "sessionId": "<sessionId>",
      "agentAddress": "<agentAddress>",
      "sessionToken": "<sessionToken>",
      "tenderId": "<tenderId>",
      "reservationId": "<reservationId>",
      "transactionHashes": "<transactionHashes>"
    },
    "name": "record_virtuals_tender_funding_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenderIdYes
sessionIdYes
agentAddressYes
sessionTokenYes
reservationIdYes
transactionHashesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=false; the description adds real context beyond them — deployment prerequisites, x402/subscription auth tier, durability of the write, and the fact it does not move funds. It omits the important implication of idempotentHint=false (behavior on repeated calls with the same hashes), which keeps it from 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?

Only two sentences, mostly front-loaded with the actual action after a short metadata header. The bracketed capability/tier/API prefix is machine-oriented metadata that consumes the lead position, but it is compact and not repeated.

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?

Covers purpose, precondition, and non-submission, but for a destructive, non-idempotent write with six undocumented required params and no output schema, it leaves gaps: retry/duplicate behavior, required tender state, and what the response confirms are all unstated.

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 six required parameters. The description only implicitly points at transactionHashes and reservationId; it says nothing about tenderId's fdat_ format, agentAddress, sessionId, or sessionToken, nor about the 1–4 hash limit.

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+resource: 'Durably record canonical Base transaction hashes' following an ACP V2 funding reservation. It implicitly distinguishes itself from the reservation-creating sibling by specifying 'after the customer wallet submits an existing ACP V2 funding reservation', but never names reserve_virtuals_tender_funding_v2 or any other sibling explicitly.

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?

Gives a clear sequencing precondition (call after the wallet has submitted an existing funding reservation) and an explicit boundary: 'This action cannot submit a transaction itself.' No named alternatives or exclusions beyond that, which keeps it at 4 rather than 5.

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