Skip to main content
Glama
lindoai

mcp-lindoai

Official

add_workspace_team_member

Add a team member to your workspace by providing their email and assigning a role. Simplify team management within Lindo AI.

Instructions

Add a team member to the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesTeam member email
roleYesTeam member role

Implementation Reference

  • Registration of the 'add_workspace_team_member' tool on the MCP server via server.tool()
    server.tool(
      "add_workspace_team_member",
      "Add a team member to the workspace.",
      {
        email: z.string().describe("Team member email"),
        role: z.string().describe("Team member role"),
      },
      { title: "Add Team Member", readOnlyHint: false, destructiveHint: false, openWorldHint: false },
      async ({ email, role }) => {
        const data = await apiCall("/v1/workspace/team", "POST", { email, role });
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Handler function that takes email and role, calls POST /v1/workspace/team API, and returns the response
    async ({ email, role }) => {
      const data = await apiCall("/v1/workspace/team", "POST", { email, role });
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema defining parameters: email (string) and role (string), both described via Zod
    {
      email: z.string().describe("Team member email"),
      role: z.string().describe("Team member role"),
    },
Behavior2/5

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

While annotations indicate readOnlyHint=false and destructiveHint=false, the description adds no additional behavioral context. It does not explain side effects, such as whether duplicate emails are rejected or if roles are validated. The description is minimal beyond the action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no unnecessary words. It is front-loaded and easy to read. However, it could be slightly more structured by including brief param context.

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

Completeness2/5

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

For a mutation tool with no output schema, the description lacks completeness. It does not provide any follow-up actions, error conditions, or post-conditions. The tool is simple, but the description is too sparse to fully inform the agent.

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 input schema covers both parameters (email and role) with descriptions, achieving 100% coverage. The description does not add extra meaning, but the schema itself is sufficient. Baseline score of 3 is appropriate.

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 action (add) and the resource (team member to the workspace). It distinguishes from the sibling 'remove_workspace_team_member' but does not differentiate from other 'add' tools like 'add_custom_domain'. However, the resource is specific.

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?

The description provides no guidance on when to use this tool vs alternatives. It does not mention prerequisites, conditions, or when not to use it. There is no mention of the context for adding a team member.

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