Skip to main content
Glama
lovieco

Lovie Company Formation MCP

Official
by lovieco

lovie_auth_required

Run npx lovie login in your terminal to authenticate and unlock company formation, banking, cards, and invoices.

Instructions

The user is not authenticated with Lovie. Tell them to run npx lovie login in their terminal to authenticate, then restart the MCP connection. All Lovie tools (company formation, banking, cards, invoices) will become available after login.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:730-738 (registration)
    Tool object definition (name, description, inputSchema) for lovie_auth_required. Registered as a RemoteTool constant.
    const AUTH_REQUIRED_TOOL: RemoteTool = {
      name: "lovie_auth_required",
      description:
        "The user is not authenticated with Lovie. Tell them to run `npx lovie login` in their terminal to authenticate, then restart the MCP connection. All Lovie tools (company formation, banking, cards, invoices) will become available after login.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
    };
  • Handler logic for lovie_auth_required in the CallToolRequestSchema handler. Returns an error response telling the user to run `npx lovie login`.
    // Handle the auth-required helper tool
    if (name === "lovie_auth_required") {
      return {
        content: [
          {
            type: "text" as const,
            text: "Not authenticated with Lovie. The user needs to run `npx lovie login` in their terminal to authenticate, then restart the MCP connection (e.g. `/mcp` in Claude Code). After login, all Lovie tools will be available.",
          },
        ],
        isError: true,
      };
    }
  • src/index.ts:769-774 (registration)
    tools/list handler that exposes lovie_auth_required when not authenticated or when no tools are discovered.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      if (notAuthenticated || discoveredTools.length === 0) {
        return { tools: [AUTH_REQUIRED_TOOL] };
      }
      return { tools: discoveredTools };
    });
  • RemoteTool interface defining the shape used by the tool definition.
    interface RemoteTool {
      name: string;
      description?: string;
      inputSchema: Record<string, unknown>;
    }
Behavior4/5

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

With no annotations, the description carries full burden. It clearly describes the tool's informational behavior and the required user action. It does not disclose any side effects, but for a simple notification tool, this is sufficient. No contradiction.

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 extremely concise—two sentences—and front-loaded with the key message. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, no output schema, and a simple informational purpose, the description is complete. It tells the user exactly what to do and what to expect.

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?

There are zero parameters, and schema coverage is 100%. Per guidelines, baseline is 4. The description does not add parameter info, but none is 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 explicitly states the tool's purpose: to indicate that the user is not authenticated and to provide a specific command to authenticate. It specifies the action and outcome.

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 clearly tells when to use the tool (when user is not authenticated) and what the user should do (run `npx lovie login`). It also explains the result: all Lovie tools become available after login. No sibling tools exist, so differentiation is not needed.

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

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/lovieco/lovie-company-formation-mcp-npx'

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