Skip to main content
Glama

list_team

View team members and their roles to manage team structure and access permissions within the Cuti-E admin platform.

Instructions

List all team members with their roles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for "list_team" tool, which executes a GET request to the "/v1/team" API endpoint.
    case "list_team": {
      result = await apiRequest("GET", "/v1/team");
      break;
    }
  • index.js:257-264 (registration)
    The registration block for "list_team" tool, defining its name, description, and empty input schema.
      name: "list_team",
      description:
        "List all team members with their roles.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists team members, implying a read-only operation, but doesn't cover aspects like pagination, rate limits, authentication needs, or error handling. This is a significant gap for a tool with zero annotation coverage.

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, efficient sentence: 'List all team members with their roles.' It's front-loaded with the core action and resource, with zero wasted words, making it highly concise and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavior, output format, or usage context. For a basic list tool, this is borderline complete but leaves gaps that could hinder effective agent use.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, but since there are no parameters, this is acceptable. A baseline of 4 is appropriate as the description doesn't need to compensate for missing param info.

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 tool's purpose: 'List all team members with their roles.' It uses a specific verb ('List') and identifies the resource ('team members with their roles'). However, it doesn't explicitly distinguish itself from sibling tools like 'get_active_users' or 'get_active_users_all_apps,' which might have overlapping functionality, preventing a perfect score.

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 versus alternatives. It doesn't mention prerequisites, exclusions, or compare it to siblings such as 'get_active_users' or 'get_active_users_all_apps,' leaving the agent to infer usage based on name alone.

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/Stig-Johnny/cutie-mcp'

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