Skip to main content
Glama

purchase_firstparty_catalog_item

[EN] Instant purchase & cryptographic delivery of TrustGate Official First-Party curated packages (Institutional CME Globex NQ microstructure, Sourcify Solidity blueprints, Enterprise RAG/Skill Firewall, Retail Anti-Rugpull & Zero-Lookahead Starter Packs from 1 USDC). | [ES] Compra y entrega instantánea de paquetes oficiales de TrustGate (Institucional y Retail desde 1 USDC). | [中文] 即时购买并获取 TrustGate 官方认证精选数据包(芝商所 NQ 微观结构、Sourcify 智能合约蓝图、企业级 RAG 防毒包及 1 USDC 起的零售反貔貅工具包)。

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
itemIdYesID of the curated First-Party package to purchase.
buyerIdNoBuyer agent ID (optional).
paymentTokenNo
paymentTxHashNoBase 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only markets 'instant purchase & cryptographic delivery'. It never states that payment is irreversible/non-refundable, what happens on payment failure or delivery failure, whether an item can be re-downloaded, or any auth requirements. The 402 Payment Invoice flow is disclosed only in the input schema, not in the description.

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

Conciseness2/5

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

The content is triplicated across English, Spanish and Chinese with heavy marketing adjectives ('Zero-Lookahead', 'Anti-Rugpull', '防毒包') rather than being front-loaded with actionable facts. The three-language repetition consumes most of the text without adding decision-relevant information.

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?

For a payment/mutation tool with no annotations and no output schema, the description should explain payment requirements, irreversibility, and delivery semantics. Those are absent, leaving an agent to infer them from the schema's paymentTxHash note; the return shape after successful delivery is undocumented anywhere.

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 75%, just under the high-coverage baseline, and the description adds essentially no parameter meaning: it never explains paymentToken choices, the optional buyerId, or the required paymentTxHash proof-of-payment concept beyond the schema's own text. The package names it lists do loosely correspond to itemId enum values, giving marginal reinforcement.

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 names a specific verb and resource: purchase plus instant cryptographic delivery of TrustGate 'First-Party curated packages', and it enumerates the package families that map onto the itemId enum. It does not explicitly contrast itself with escrow-based siblings like open_escrow_job or discover_verified_stores, but the 'First-Party' framing gives an agent enough to distinguish a direct purchase from an escrowed job.

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 when-to-use or when-not-to-use guidance and no named alternative. The only usage-ish signal is a price floor ('from 1 USDC'), which does not tell an agent whether to buy here instead of opening an escrow job or auditing an existing escrow.

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.