Skip to main content
Glama

veritas-8183-agent-notary-witness

purchase_firstparty_catalog_item

[Private] Buy an official dataset, security scanner or tutorial pack, paid in USDC on Base and delivered decrypted. Example: itemId='retail-anti-rugpull-scanner-pack-v06'. Call with {} for a free read-only sample preview.

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": "purchase_firstparty_catalog_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdNoCatalog package identifier to unlock.
buyerIdNoBuyer agent ID claiming the package.
paymentTokenNoSettlement token symbol.
paymentTxHashNoBase Mainnet USDC transaction hash (0x...) paying the package price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "itemId"
      -]New value: +[]
  2. Changed6 schema fields changed
    • changedInput schema / properties / buyerId / description
      Previous value: -"Buyer agent ID (optional)."New value: +"Buyer agent ID claiming the package."
    • changedInput schema / properties / itemId / description
      Previous value: -"ID of the curated First-Party package to purchase."New value: +"Catalog package identifier to unlock."
    • changedInput schema / properties / itemId / enum
      Previous value: -[
      -  "inst-cme-nq-microstructure-v06",
      -  "inst-sourcify-erc8183-vault-v06",
      -  "inst-enterprise-rag-skill-firewall-v06",
      -  "retail-anti-rugpull-scanner-pack-v06",
      -  "retail-nq-quant-starter-backtest-v06",
      -  "retail-safe-mcp-skill-starter-v06"
      -]New value: +[
      +  "inst-cme-nq-microstructure-v06",
      +  "inst-solidity-0838-vault-blueprint-v06",
      +  "inst-enterprise-rag-skill-firewall-v06",
      +  "retail-anti-rugpull-scanner-pack-v06",
      +  "retail-nq-crypto-clean-backtest-v06",
      +  "retail-safe-mcp-skills-starter-v06",
      +  "retail-veritas-level3-mastery-tutorial-v07"
      +]
    • addedInput schema / properties / paymentToken / description
      Added value: +"Settlement token symbol."
    • changedInput schema / properties / paymentToken / enum
      Previous value: -[
      -  "USDC",
      -  "SOL",
      -  "ETH",
      -  "VIRTUAL",
      -  "USDT"
      -]New value: +[
      +  "USDC",
      +  "ETH",
      +  "SOL",
      +  "VIRTUAL",
      +  "USDT"
      +]
    • changedInput schema / properties / paymentTxHash / description
      Previous value: -"Base Mainnet (Chain ID 8453) USDC transfer transaction hash (0x...) paying the exact item price to Treasury 0x861Ac49F8299C45Cca6bD9F0254080Fd82061Ac4. If omitted on external HTTP calls, returns a 402 Payment Invoice."New value: +"Base Mainnet USDC transaction hash (0x...) paying the package price."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond annotations, it adds important behavior: payment settles in USDC on Base, the item is delivered decrypted, and an empty request returns a free sample preview. It does not address non-idempotency or whether spending funds is reversible, despite idempotentHint=false in annotations.

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?

Two sentences, front-loaded with the purchase purpose, then a concrete example and the free-preview behavior. There is no unnecessary wording.

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 purchase tool with no output schema, the description covers the core purpose, payment chain, delivery mode, and preview path. It still leaves out price, delivery format after purchase, and refund or failure behavior, which matter for an agent spending funds.

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 the baseline is 3. The example itemId and empty-call preview add some value, but the description says payment is USDC-only while the schema paymentToken enum permits ETH, SOL, VIRTUAL, and USDT, creating a potential conflict.

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: buying an official dataset, security scanner, or tutorial pack from a catalog. It expands the tool name meaningfully but does not explicitly distinguish itself from sibling audit, discovery, or escrow tools.

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 gives clear purchase context, identifies USDC-on-Base payment, and explicitly says to call with an empty object for a free read-only sample preview. It does not state when not to use it or name an alternative tool.

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.