Skip to main content
Glama
lindoai

mcp-lindoai

Official

generate_magic_link

Create a secure magic link for client login using a client ID, simplifying authentication.

Instructions

Generate a magic login link for a client.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_idYesClient ID

Implementation Reference

  • The tool handler for generate_magic_link. Registers an MCP tool that accepts a client_id, calls the /v1/workspace/client/magic-link API endpoint via POST, and returns the JSON result.
    server.tool(
      "generate_magic_link",
      "Generate a magic login link for a client.",
      {
        client_id: z.string().describe("Client ID"),
      },
      { title: "Generate Magic Link", readOnlyHint: false, destructiveHint: false, openWorldHint: false },
      async ({ client_id }) => {
        const data = await apiCall("/v1/workspace/client/magic-link", "POST", { client_id });
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The apiCall helper function used by the handler to make authenticated HTTP requests to the backend API.
    async function apiCall(path, method, body) {
      const url = `${BASE_URL}${path}`;
      const res = await fetch(url, {
        method,
        headers: {
          Authorization: `Bearer ${API_KEY}`,
          "Content-Type": "application/json",
        },
        ...(body ? { body: JSON.stringify(body) } : {}),
      });
      return res.json();
    }
Behavior3/5

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

Annotations already indicate this is not read-only and not destructive. The description does not add behavioral details beyond stating the action, which is consistent with annotations.

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?

Extremely concise single sentence with no wasted words. Information is immediately clear.

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 simple tool with one parameter and no output schema, the description provides essential information. Minor gap: no mention of return value or side effects, but sufficient for the action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with 'Client ID' described. The description does not add any additional meaning to the parameter, so baseline of 3 is appropriate.

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 clearly states the action ('Generate'), the resource ('magic login link'), and the target ('for a client'). It distinguishes itself from sibling tools, none of which perform this specific function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives or prerequisites. The usage is implied but not expanded upon.

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/lindoai/mcp-server'

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