Skip to main content
Glama
Sign In

Sorsa

by app.sorsa
OverviewDiscussionsAdmin

queue_checkout

Queue an Amazon checkout on the user's own desktop Chrome (requires the Sorsa extension installed and signed in there). Call when the user says e.g. 'buy 3 of this' or 'replen this ASIN at up to £20'. mode 'review' (default) drives to Amazon's review page and STOPS — the user clicks Place Order themselves. mode 'auto' places the order, but only if the user has enabled Auto checkout in the extension popup AND the order total is within max_price × qty (max_price is required for auto). max_price is ALWAYS in GBP (£) per unit, whatever the marketplace — the server converts it to the local currency at the current rate, so '£20 max on amazon.de' just works. pace 'calm' (default) clicks at a relaxed human pace — use 'fast' only for time-sensitive deals. domain is the marketplace: GB, US, DE, FR, ES or IT. The job expires after 15 minutes if the user's desktop isn't online to claim it. Always tell the user what was queued and that their desktop Chrome will open it.

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": {
      "asin": "<asin>"
    },
    "name": "queue_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNo
asinYes
modeNoreview
paceNocalm
domainNoGB
max_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well: it discloses that review mode stops before Place Order, that auto mode has an extension-side precondition and a price ceiling, that max_price is GBP per unit and server-converted to local currency, that jobs expire after 15 minutes if the desktop is offline, and that the agent must report back what was queued. These are exactly the side effects and failure modes an agent needs before invoking a purchasing tool.

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

Conciseness4/5

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

Front-loaded with the purpose and the default-safe mode before the caveats, and nearly every clause adds operational constraint rather than filler. It is on the long side and the ragged line breaks around 'pace calm (default)' hurt scanability slightly, but no sentence is expendable.

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 high-risk mutation tool with no annotations and no output schema, the description covers preconditions, both execution modes and their guardrails, currency semantics, timeout behavior, and a required post-call user notification. An agent could invoke this correctly without consulting anything else.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must supply all parameter meaning, and it does: mode values with defaults and semantics, pace values with defaults and when to escalate, domain as the enumerated marketplace set (GB, US, DE, FR, ES, IT), and max_price's currency, unit basis (per unit), conversion behavior, and requirement under auto mode. Only asin and qty are covered implicitly rather than defined, which is a minor residue against an otherwise complete mapping.

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 ('Queue an Amazon checkout on the user's own desktop Chrome') and names the mechanism (Sorsa extension). This is immediately distinguishable from siblings like add_purchase or get_amazon_orders, which read records rather than drive a live browser checkout.

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?

Gives concrete trigger phrases ('buy 3 of this', 'replen this ASIN at up to £20') plus the prerequisite that the extension must be installed and signed in. It also routes between its own modes: 'review' is the default and stops at the review page, 'auto' only when the user enabled Auto checkout and the total is within max_price × qty, and 'fast' pace is reserved for time-sensitive deals.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sorsa toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources