Skip to main content
Glama
ananddtyagi

Webpage Screenshot MCP Server

signal-login-complete

Indicates completion of manual login to resume automated processes in the Webpage Screenshot MCP Server, ensuring continuity in web application verification.

Instructions

Signals that manual login is complete and the login-and-wait tool should continue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'signal-login-complete' tool. It creates a temporary file in the system's temp directory to signal that the manual login process is complete, allowing the 'login-and-wait' tool to proceed. Returns a success message or error response.
    async () => {
        try {
            const completionFile = path.join(os.tmpdir(), 'mcp-login-complete.txt');
            await fsPromises.writeFile(completionFile, 'complete');
            
            return {
                content: [
                    {
                        type: "text",
                        text: "Login completion signal sent! The login-and-wait tool should continue shortly."
                    }
                ],
            };
        } catch (error) {
            const errorMessage = error instanceof Error ? error.message : String(error);
            return {
                isError: true,
                content: [
                    {
                        type: "text",
                        text: `Error signaling login completion: ${errorMessage}`,
                    },
                ],
            };
        }
    }
  • src/index.ts:654-684 (registration)
    The registration of the 'signal-login-complete' tool using server.tool(), including the tool name, description, empty input schema ({}), and inline handler function.
    server.tool(
        "signal-login-complete",
        "Signals that manual login is complete and the login-and-wait tool should continue",
        {},
        async () => {
            try {
                const completionFile = path.join(os.tmpdir(), 'mcp-login-complete.txt');
                await fsPromises.writeFile(completionFile, 'complete');
                
                return {
                    content: [
                        {
                            type: "text",
                            text: "Login completion signal sent! The login-and-wait tool should continue shortly."
                        }
                    ],
                };
            } catch (error) {
                const errorMessage = error instanceof Error ? error.message : String(error);
                return {
                    isError: true,
                    content: [
                        {
                            type: "text",
                            text: `Error signaling login completion: ${errorMessage}`,
                        },
                    ],
                };
            }
        }
    );
  • The input schema for the tool, which is empty object indicating no input parameters are required.
    {},
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the behavioral trait of signaling completion to another tool, which is useful context. However, it doesn't disclose other aspects like whether it requires specific permissions, has side effects, or how it interacts with authentication states, leaving some gaps.

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 a single, efficient sentence that front-loads the key information: signaling login completion. There is zero waste, and it earns its place by clearly stating the tool's role in the workflow.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is complete enough. It explains the purpose and usage in context with sibling tools. However, it could be slightly more complete by mentioning any prerequisites or effects, but for a signaling tool, this is adequate.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, but this is acceptable given the lack of parameters. Baseline is 4 for 0 params, as it doesn't need to compensate for any gaps.

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 clearly states the tool's purpose: to signal completion of manual login so another tool (login-and-wait) can continue. It specifies the verb 'signals' and the context 'manual login is complete,' but doesn't explicitly differentiate from all sibling tools like clear-auth-cookies or screenshot tools, which serve different purposes.

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 explicitly states when to use this tool: 'when manual login is complete' and that it should be used to allow 'login-and-wait tool should continue.' It names the specific alternative tool (login-and-wait) and implies usage in a sequence, providing clear context without exclusions.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ananddtyagi/webpage-screenshot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server