Lazada Community MCP

Complete Lazada Sign-in

capture_session

Idempotent

Confirm when human sign-in is complete, then privately persist the session for all subsequent tasks. Call once after sign-in to enable authenticated actions.

Instructions

Check whether human sign-in has finished and persist the session privately for all tasks. No credential arguments. Call once after the user finishes; do not poll repeatedly.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Sep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond annotations, it discloses that the session is persisted privately and that no credentials are required. The idempotent/readOnly annotations are not contradicted; the 'call once' instruction supplements, rather than conflicts with, idempotentHint.

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 short sentences carry the essential information with no filler; the core behavior is front-loaded and the usage caveat is placed at the end.

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 zero-parameter tool with an output schema, the description covers purpose, persistence, timing, and polling behavior. It does not detail what happens if called too early, but the instruction to call only after the user finishes is sufficient for this tool's complexity.

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?

With zero parameters and 100% schema coverage, the description has little to add, but explicitly stating 'No credential arguments' reinforces that the tool should be called without parameters.

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 concrete action — checking completion of human sign-in and persisting the session — and is clearly distinct from login/start_login siblings that initiate sign-in. The 'No credential arguments' qualifier avoids ambiguity with credential-taking login tools.

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?

Explicitly says when to call ('after the user finishes') and adds a negative instruction ('do not poll repeatedly'). It does not name sibling alternatives such as session_status, so the routing guidance is clear but not exhaustive.

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