Skip to main content
Glama

Show Alphamega cart to the user

cart_open
Read-only

Opens the cart page in the user's Chrome so they can review their basket before checkout. Use only when the user asks to view the cart or is ready to check out.

Instructions

Bring the cart page to the front in the user's Chrome. This takes over their screen, so call it only when the user asks to see the cart or is ready to check out — not as a routine last step. Checkout, delivery slot and payment are always done by the user; this server cannot place orders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cart_open"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover safety (readOnlyHint, openWorldHint) but say nothing about the disruptive UI takeover, which the description usefully discloses as "takes over their screen." It also draws a capability boundary the annotations cannot convey: checkout, delivery slot and payment are user-performed and the server cannot place orders. It omits what happens without an active browser session (relevant given a cart_login sibling), so not a 5.

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 sentences, front-loaded with the action, then the caution, then the capability limit. Every sentence adds distinct information with no repetition of the title.

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?

For a simple, zero-parameter, no-output tool, the description covers what it does, when to call it, its side effect on the user's screen, and what it cannot do. The remaining gap is failure/authentication behavior in the browser session, which an agent might need if no session is open.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter claims are made or contradicted.

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

Purpose4/5

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

The description gives a specific verb and target ("Bring the cart page to the front in the user's Chrome"), which is concrete and actionable. However, a sibling named cart_view exists and the description never distinguishes this UI-foregrounding tool from that potentially similar-sounding one, leaving a real ambiguity an agent could stumble on.

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 states both the trigger (user asks to see the cart, or is ready to check out) and an explicit prohibition ("not as a routine last step"), which is strong conditional guidance. It stops short of naming an alternative sibling for the read-the-cart-contents case, so a 4 rather than a 5.

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