Skip to main content
Glama

StoreTechScan — Ecommerce Tech Stack & ICP

Claim Purchased StoreTechScan Credits

claim_purchase
Idempotent

Poll a purchase created by buy_credits using the agent-held session_id and claim_token. While ready is false, wait retry_after_seconds before retrying (up to 15 minutes). Once the human has paid, returns the API key for the agent to store securely and use in the MCP connection or REST Authorization header. Keep the claim token out of the browser; key retrieval can be retried from the same IP for 15 minutes after the first successful claim.

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": {
      "session_id": "<session_id>",
      "claim_token": "<claim_token>"
    },
    "name": "claim_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
claim_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior; the description goes further by explaining the polling loop, the 15-minute window, and that key retrieval can be retried from the same IP after a successful claim, which substantiates the idempotent hint. It also discloses a security constraint (keep the claim token out of the browser) and the storage obligation for the returned key. This is real added context beyond the annotations, though it does not cover failure/expiry behavior after the 15-minute window.

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?

Four sentences, front-loaded with the action and its source, then polling behavior, then the return value and its handling. Every sentence carries operational or security information with no restatement of the tool name or schema.

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 correctly specifies the return value (the API key) and how to use it (MCP connection or REST Authorization header). Combined with the retry window and secret-handling guidance, an agent has everything needed to call this correctly and securely.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden, and it does add meaning: session_id is framed as 'agent-held' and originating from buy_credits, and claim_token is framed as a secret that must not reach the browser. It stops short of format, length, or validation details for either string 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?

States a specific verb and resource ('Poll a purchase created by buy_credits') and names the sibling that creates the input, so an agent can place it in the workflow without opening another schema. It also names the outcome ('returns the API key'), which distinguishes it from check_credits and buy_credits.

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?

The precondition is explicit: this is called on a purchase created by buy_credits, using the agent-held session_id and claim_token. It also gives concrete operational guidance for the not-ready case (wait retry_after_seconds, up to 15 minutes). There is no explicit 'do not use when' or named alternative for failure paths, which keeps it short of a 5.

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