Skip to main content
Glama

ASO Studio Live Domain Audit & Self-Serve ASO Pack

Create a pack order

create_aso_pack_order

Create an unpaid $19 Express 8-file or $49 Self-Serve 26-file ZIP order. Returns order_ref, Base Mainnet USDC details, x402 URL and no-account AnonPay XMR URL. No payment is sent; XMR is verified within 24h. Reuse idempotency_key to recover a retry.

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": {
      "domain": "<domain>"
    },
    "name": "create_aso_pack_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesPublic domain, for example example.com; private hosts are rejected.
tier_slugNoExpress costs 19.00 USDC; Self-Serve costs 49.00 USDC.self-serve-pack
payment_methodNoUSDC on Base Mainnet or Monero via AnonPay.usdc_erc20
idempotency_keyNoStable key for retries of this order; omit to create a new order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that this mutating call charges nothing immediately, that XMR settlement is verified asynchronously within 24h, and exactly what the payload contains (order_ref, Base Mainnet USDC details, x402 URL, AnonPay XMR URL). The idempotency-retry note is a useful nuance even though idempotentHint is false — it explains key-based recovery rather than automatic deduplication.

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?

Three dense sentences, zero filler, with the pricing/size distinction front-loaded and the payment semantics and retry rule following in priority order. Every sentence carries information an agent needs.

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

Completeness5/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 takes on the burden of describing the return payload and does so explicitly, plus the asynchronous payment-verification behavior. For a four-parameter, open-world mutation tool this covers everything needed to invoke it correctly.

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 all four parameters are already documented in the schema, including the enum values and defaults. The description adds only the file counts (8-file / 26-file) alongside the prices, which is marginal extra meaning over the schema's own tier descriptions. Baseline 3 is appropriate.

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?

States a specific verb and resource plus concrete scope: 'Create an unpaid $19 Express 8-file or $49 Self-Serve 26-file ZIP order.' The pricing/tier detail makes it immediately distinguishable from sibling tools like claim_aso_pack_download or generate_domain_aso_router without opening the schema.

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?

Gives explicit operational guidance: no payment is sent at creation, XMR is verified within 24h, and idempotency_key should be reused to recover a retry. It does not explicitly name when to prefer this over siblings (e.g., the follow-up claim tool), so it stops short of full when/when-not routing.

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