Skip to main content
Glama

StoreTechScan — Ecommerce Tech Stack & ICP

Buy StoreTechScan Credits

buy_credits

Create a one-time credit pack checkout for a human to pay in their browser. Show only checkout_url to the human; keep session_id and claim_token with the agent and never put claim_token in a browser URL. After payment, poll claim_purchase every 10–15 seconds for up to 15 minutes. The API key appears only in the claim_purchase tool result, once with a 15-minute same-IP retry grace window. To top up an existing account, authenticate this MCP connection with its Bearer or X-API-Key header before calling.

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": {
      "package_id": "<package_id>"
    },
    "name": "buy_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoOptional buyer email for checkout.
package_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (which only say non-read-only, open-world, non-idempotent), the description discloses the security-critical behavior: show only checkout_url to the human, keep session_id and claim_token private, never place claim_token in a browser URL. It also explains that the API key appears exactly once in the claim_purchase result with a 15-minute same-IP retry grace window, which is essential operational context an agent cannot infer.

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?

Five short sentences, each doing distinct work: purpose, output handling, follow-up polling, secret delivery, and auth precondition. It is front-loaded with the purpose and contains no filler or repetition.

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?

For a payment-flow tool with no output schema, the description covers everything an agent needs: what to surface to the human, what to retain privately, how to obtain the resulting key, the timing of the retry window, and the auth prerequisite for top-ups. Remaining unknowns (failure modes, pricing) are minor relative to this coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%, and the description adds nothing about either parameter. It never explains what package_id selects (the starter/growth/agency enum, which lives only in the schema) or what the optional email is used for, so it fails to compensate for the coverage gap on the sole required parameter.

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 first sentence states a specific verb and resource ('Create a one-time credit pack checkout') and immediately names the actor and channel ('for a human to pay in their browser'). This distinguishes it cleanly from the sibling claim_purchase, which the description later names as the follow-up step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit sequencing: call this to create checkout, then poll claim_purchase every 10-15 seconds for up to 15 minutes. It also states a precondition for the top-up case (authenticate the MCP connection with Bearer or X-API-Key before calling), covering both when to use and how to proceed.

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