Skip to main content
Glama

View Alphamega cart

cart_view
Read-only

Reads the current Alphamega basket, including item lines, quantities, unit prices, totals, and login status so agents can inspect and verify shopping carts.

Instructions

Read the current cart on alphamega.com.cy: lines (id, title, quantity, unit price, line total) and the order summary (subtotal, delivery, order total). Also reports whether the browser is logged in.

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_view"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=true already tell the agent this is a safe external read, so the description's marginal load is lower. It adds value by disclosing the exact returned contents and the login-state side signal, but says nothing about empty-cart behavior, failure modes, or whether a browser must already be open.

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?

Opens with the action and target, then a compact parenthetical field list, then a one-clause note about login state. No filler, though the field enumeration is dense enough to read as a run-on.

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?

With no output schema, the description carries the return-value burden and does so by listing line fields and summary fields. Missing only edge-case behavior (empty cart, not-logged-in results, errors) for an otherwise simple zero-parameter read.

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 beyond what the empty schema shows. Baseline for a parameterless tool applies.

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?

States a specific verb ('Read') and resource ('the current cart on alphamega.com.cy') and enumerates the returned line and summary fields, so the agent knows exactly what it gets. It never names a sibling (cart_set, cart_clear) as the write alternative, so differentiation is implied by the word 'Read' rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: 'Read the current cart' signals inspection, and 'Also reports whether the browser is logged in' hints at a pre-check role before cart_login or cart_set. There is no explicit when-to-use, when-not-to-use, or named alternative.

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