Skip to main content
Glama

ASO Studio Live Domain Audit & Self-Serve ASO Pack

Claim a settled pack

claim_aso_pack_download
Idempotent

Verify a Base USDC transaction or check order status with its download_token. Returns a direct ZIP URL, actual archive file manifest and receipt only after settlement. Pending, mismatched or replayed payments never unlock a pack.

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": {
      "order_ref": "<order_ref>"
    },
    "name": "claim_aso_pack_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_hashNoSettled Base Mainnet transaction hash; omit when checking status with download_token.
order_refYesReference returned by create_aso_pack_order.
download_tokenNoOrder-specific capability from signed_deliverable_zip_url, required if tx_hash is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: nothing is returned until settlement, replay attempts are rejected, and the response includes a receipt plus an actual archive manifest. It doesn't mention auth requirements or rate limiting, but those are secondary here.

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, both load-bearing. The dual-mode purpose comes first, followed by the exact return payload and the settlement gate, with no filler wording.

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

Completeness4/5

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

There is no output schema, so the description usefully enumerates what comes back (direct ZIP URL, archive manifest, receipt). It leaves open what the tool returns on a pending or mismatched payment, but the gating rule itself is stated, making the definition adequate for a three-parameter 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 description coverage is 100%, and the schema already explains that tx_hash is omitted when using download_token. The description reinforces the tx_hash/download_token branching but adds no format, precedence, or edge-case detail beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

The description states a specific action and resource: verify a Base USDC transaction or check order status, then unlock a pack download. It names the two input modes and the gated outcome (ZIP URL, manifest, receipt), which is enough to place it after create_aso_pack_order rather than confusing it with the scoring/probe siblings.

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 usage context: the tool is used either to verify a settlement transaction or to poll status with a download_token, and it states the failure condition (pending, mismatched, replayed payments). It stops short of explicitly naming create_aso_pack_order as the required predecessor in the prose, leaving that to the order_ref parameter description.

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.

Resources