Skip to main content
Glama
lindoai

mcp-lindoai

Official

remove_workspace_team_member

Destructive

Remove a workspace team member by specifying their member ID. This tool deletes the user and revokes their access.

Instructions

Remove a team member from the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
member_idYesTeam member ID to remove

Implementation Reference

  • The async handler function that executes the remove_workspace_team_member tool logic. It calls apiCall to DELETE /v1/workspace/team/{member_id}.
    async ({ member_id }) => {
      const data = await apiCall(`/v1/workspace/team/${member_id}`, "DELETE");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Zod schema defining the input parameter: member_id (string) - the team member ID to remove.
    {
      member_id: z.string().describe("Team member ID to remove"),
    },
  • Registration of the remove_workspace_team_member tool on the MCP server, including its title, description, and metadata (destructiveHint: true).
    server.tool(
      "remove_workspace_team_member",
      "Remove a team member from the workspace.",
      {
        member_id: z.string().describe("Team member ID to remove"),
      },
      { title: "Remove Team Member", readOnlyHint: false, destructiveHint: true, openWorldHint: false },
      async ({ member_id }) => {
        const data = await apiCall(`/v1/workspace/team/${member_id}`, "DELETE");
        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 Lindo AI 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 indicate destructiveHint=true, so the destructiveness is known. The description adds no further behavioral context beyond what annotations provide.

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?

Single sentence, front-loaded, no unnecessary words. Efficient and 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?

Given the simple input and annotations, the description is adequate. Could mention that removal is immediate or irreversible, but not necessary.

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?

The schema covers 100% of parameters with a clear description. The tool description adds no additional meaning beyond the schema.

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 'Remove a team member from the workspace' uses a specific verb and resource, clearly distinguishing it from sibling tools like add_workspace_team_member.

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

Usage Guidelines2/5

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

No guidance on when to use or not use this tool, such as permissions or constraints (e.g., cannot remove last admin).

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