Lazada Community MCP

Open Lazada Login

login

Open or reuse a visible sign-in window for user authentication, then capture the session after human sign-in. Credentials, OTPs, and captcha answers are never handled in chat.

Instructions

Start or reuse a visible sign-in window and return promptly; after human sign-in call capture_session. Never ask for or pass credentials, OTPs, or captcha answers through chat.

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": "login"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`message`	Yes
`loggedIn`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Sep 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond annotations, the description reveals that the tool opens a visible window,returns promptly, and requires human interaction. It also states a critical constraint about not handling credentials, which is valuable behavioral context not present in the structured metadata.

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?

The description is two sentences with no unnecessary words. The first sentence states the action and follow-up, and the second adds a mandatory safety constraint. It is concise and properly front-loaded.

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 zero parameters and an existing output schema, the description covers the core usage and constraints sufficiently. It could be more complete by explicitly distinguishing from the sibling 'start_login,' but the given text still provides enough context for correct invocation.

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 input schema has zero parameters and 100% coverage, so there is nothing additional for the description to explain. The description does not mention parameters, which is appropriate; the baseline of 4 applies for a parameter-less tool.

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 opens with a specific action: 'Start or reuse a visible sign-in window and return promptly,' which clearly identifies the tool's purpose and resource. It also distinguishes itself from session capture by instructing 'after human sign-in call capture_session.'

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 description gives clear workflow context: use this to start or reuse the visible window, then call capture_session after human sign-in. It also enforces a boundary with 'Never ask for or pass credentials, OTPs, or captcha answers through chat.' It does not explicitly name alternatives like start_login or session_status, so exclusions are absent.

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