Skip to main content
Glama

Open Alphamega login

cart_login

Checks whether Chrome is signed in to Alphamega and opens the login page if needed. Call it when a cart tool reports login is required; the user completes phone and SMS verification.

Instructions

Check whether the user's Chrome is signed in to Alphamega and, if not, open the login page there. The user must sign in themselves (phone number + SMS code); never ask them for the code. Call this when another cart tool reports that login is required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the annotations: readOnlyHint=false and openWorldHint=true only imply that this changes something outside the session, but the description states that this opens a browser page in the user's Chrome, that the human must complete sign-in with a phone number and an SMS code, and that the agent must never request that code. This is exactly the operational context an agent needs before invoking a login flow.

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 core behavior, then the human-in-the-loop constraint, then the invocation trigger. No filler, and each sentence adds a distinct piece of information.

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?

There is no output schema, and the description never says what the check returns, for example whether a boolean or status indicates whether the user is already signed in. Everything else, including the trigger, the side effect, and the constraint on user interaction, is covered; only the return-value contract is left to inference.

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 the input schema carries no parameter semantics for the description to explain; this dimension gets its baseline score. The description correctly implies no arguments are needed.

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 description names a specific verb and resource: it checks whether the user's Chrome session is signed in to Alphamega and, if not, opens the login page there. This is distinct from the sibling cart_* tools because it is about an authentication precondition, not about manipulating cart contents.

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?

The description gives an explicit trigger: 'Call this when another cart tool reports that login is required.' It also defines the boundary of agent responsibility: the user signs in themselves, and the agent must never ask for the SMS code. This gives both when-to-use guidance and a hard when-not-to-act constraint.

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