Skip to main content
Glama

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'.

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": {
      "itemId": "<itemId>"
    },
    "name": "purchase_firstparty_catalog_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesCatalog 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. 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."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already give readOnlyHint=false, openWorldHint=true, idempotentHint=false, which establishes a non-idempotent, externally-effectful write. The description adds meaningful context beyond that: payment is required, settlement is on Base, and delivery is decrypted — but it omits whether payment must be sent before calling, price, and reversal/refund behavior. Note a partial inconsistency: the description fixes payment to USDC on Base while the schema's paymentToken enum allows ETH, SOL, VIRTUAL and USDT.

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 tight sentences with the purchase action and delivery mechanism front-loaded; no filler. The trailing itemId example is slightly redundant with the enum and could be dropped, keeping it just short of a 5.

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?

With no output schema, the description should explain what a successful call returns (decrypted payload? delivery pointer? receipt), and it only says 'delivered decrypted'. The payment handshake — whether paymentTxHash is supplied up front or after an out-of-band USDC transfer — is left for the agent to guess on a 4-parameter, non-idempotent, funds-moving tool.

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 100%, so itemId, buyerId, paymentToken and paymentTxHash are all documented structurally; that sets the baseline at 3. The description's only parameter-level addition is a sample itemId value that already appears in the enum, and it implies USDC-only settlement without clarifying when the other paymentToken values are legal.

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 concrete verb and resource set ('Buy an official dataset, security scanner or tutorial pack') plus the settlement rail ('paid in USDC on Base and delivered decrypted') and a worked itemId example. An agent can distinguish this from the escrow/audit siblings, though it never names an alternative 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?

Usage is only implied by the verb 'Buy' — an agent infers it is the purchase step after discovery/quoting, but there is no stated when-to-use, no prerequisite ordering (e.g. whether a quote or escrow must exist first), and no when-not-to-use guidance.

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.