Skip to main content
Glama

notarize_and_witness_a2a_deal

[Public record, private content] Get a signed receipt that proves a deal between two agents happened, or buy a small paid service (0.10-1.00 USDC). Example: serviceId='x402-veritas-deal-witness-acta'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "notarize_and_witness_a2a_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerIdNoBuyer agent identifier.
serviceIdNoMicro-bazaar service or notary action to execute.
paymentTxHashNoBase Mainnet USDC transfer transaction hash (0x...).
sellerStoreIdNoCounterparty seller store identifier.
dealAmountUsdcNoTransaction value in USDC being witnessed.
deliverableSha256NoSHA-256 hash of the delivered payload.
clientRatingOutOf5NoVerified buyer rating (1.0 to 5.0) for the seller.
clientReviewCommentNoShort post-delivery review note.
targetSectorOrKeywordNoSingle sector or keyword to unlock when serviceId is 'x402-radar-single-sector-intel'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / buyerId / description
      Added value: +"Buyer agent identifier."
    • addedInput schema / properties / clientRatingOutOf5 / description
      Added value: +"Verified buyer rating (1.0 to 5.0) for the seller."
    • addedInput schema / properties / clientReviewComment / description
      Added value: +"Short post-delivery review note."
    • addedInput schema / properties / dealAmountUsdc / description
      Added value: +"Transaction value in USDC being witnessed."
    • addedInput schema / properties / deliverableSha256 / description
      Added value: +"SHA-256 hash of the delivered payload."
    • changedInput schema / properties / paymentTxHash / description
      Previous value: -"Base Mainnet (Chain ID 8453) USDC transfer tx hash (0x...) to Treasury 0x861Ac49F8299C45Cca6bD9F0254080Fd82061Ac4."New value: +"Base Mainnet USDC transfer transaction hash (0x...)."
    • addedInput schema / properties / sellerStoreId / description
      Added value: +"Counterparty seller store identifier."
    • addedInput schema / properties / serviceId / description
      Added value: +"Micro-bazaar service or notary action to execute."
    • changedInput schema / properties / targetSectorOrKeyword / description
      Previous value: -"Required when serviceId is 'x402-radar-single-sector-intel': specify ONE (1) single sector or keyword to unlock WHO searched and HOW MANY TIMES ('ALL' is prohibited)."New value: +"Single sector or keyword to unlock when serviceId is 'x402-radar-single-sector-intel'."
  2. Changed2 schema fields changed
    • changedInput schema / properties / serviceId / enum
      Previous value: -[
      -  "x402-veritas-deal-witness-acta",
      -  "x402-veritas-level3-star-exam",
      -  "x402-micro-antirug-token-scan",
      -  "x402-finops-llm-cost-optimizer",
      -  "x402-veritas-level3-step-by-step-tutorial"
      -]New value: +[
      +  "x402-veritas-deal-witness-acta",
      +  "x402-veritas-level3-star-exam",
      +  "x402-micro-antirug-token-scan",
      +  "x402-finops-llm-cost-optimizer",
      +  "x402-veritas-level3-step-by-step-tutorial",
      +  "x402-radar-single-sector-intel"
      +]
    • addedInput schema / properties / targetSectorOrKeyword
      Added value: +{
      +  "description": "Required when serviceId is 'x402-radar-single-sector-intel': specify ONE (1) single sector or keyword to unlock WHO searched and HOW MANY TIMES ('ALL' is prohibited).",
      +  "type": "string"
      +}
  3. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is largely covered. The description earns credit for disclosing the price band (0.10–1.00 USDC) and the 'public record, private content' disclosure framing, which annotations do not convey. However, it says nothing about the non-idempotent retry risk of a paid, chain-anchored write — a meaningful omission for a tool that consumes USDC via paymentTxHash.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no padding, but the bracketed '[Public record, private content]' tag is unexplained and sits ahead of the actual purpose, hurting front-loading. The dual 'do X, or buy Y' construction also delays comprehension of the primary function.

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

Completeness2/5

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

Nine parameters with zero required fields and no output schema means the agent must know which parameter combinations apply to which serviceId — for example that targetSectorOrKeyword only matters for the radar service, or which fields the witness receipt needs. None of this is explained, and the description does not say what the returned receipt contains or how a payment is validated. For a paid, non-idempotent write tool this is a substantial gap.

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% across all nine parameters, including the serviceId enum, so the schema carries the semantics. The description adds only the price range and one concrete example serviceId value, which is marginal added meaning over the structured fields. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names two distinct capabilities — producing a signed receipt that a deal between two agents occurred, and purchasing a paid micro-service for 0.10–1.00 USDC — which are bundled under one name without clarifying the relationship. An agent can guess the theme but cannot cleanly separate this from siblings such as audit_agent_skill_escrow or inspect_veritas_8183_seal, since no differentiating statement is made.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus the many audit_*_escrow or purchase_firstparty_catalog_item siblings, and no stated preconditions for either mode. The single example (serviceId='x402-veritas-deal-witness-acta') hints at one path but does not explain when the notarization flow applies versus the paid-service flow.

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.