Skip to main content
Glama
lindoai

mcp-lindoai

Official

get_workspace_team

Read-only

Retrieve all team members from the Lindo AI workspace.

Instructions

Get workspace team members.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration for 'get_workspace_team' using server.tool() method with metadata.
    server.tool(
      "get_workspace_team",
      "Get workspace team members.",
      {},
      { title: "Get Workspace Team", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async () => {
        const data = await apiCall("/v1/workspace/team", "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Handler function that calls apiCall to GET /v1/workspace/team and returns the result as JSON text.
    async () => {
      const data = await apiCall("/v1/workspace/team", "GET");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Helper function apiCall that makes 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();
    }
  • Empty schema object (no parameters) for get_workspace_team tool.
    {},
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description adds minimal behavioral context beyond stating it's a retrieval operation.

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 concise sentence with no wasted words, effectively conveying the tool's purpose.

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

Completeness3/5

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

While the description is adequate for a zero-parameter read tool, it lacks context about which workspace is targeted or output format, especially with no output schema.

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?

With zero parameters, the description naturally does not add parameter details, aligning with the baseline score of 4 for tools with no parameters.

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 'Get workspace team members' clearly states the action (get) and resource (workspace team members), distinguishing it from sibling tools like add_workspace_team_member and remove_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 usage guidelines are provided; the description does not specify when to use this tool over alternatives or address any preconditions.

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