Skip to main content
Glama

esa_get_members

Retrieve a list of team members from the esa platform, with options to paginate results for efficient management.

Instructions

Get a list of team members

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to retrieve
per_pageNoNumber of results per page (default: 20, max: 100)

Implementation Reference

  • Handler for the 'esa_get_members' tool call within the CallToolRequest switch statement. Parses arguments and invokes esaClient.getMembers to fetch team members.
    case "esa_get_members": {
      const args = request.params.arguments as unknown as GetMembersArgs;
      const response = await esaClient.getMembers(args.page, args.per_page);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool schema definition for 'esa_get_members', including name, description, and input schema for pagination parameters.
    const getMembersTool: Tool = {
      name: "esa_get_members",
      description: "Get a list of team members",
      inputSchema: {
        type: "object",
        properties: {
          page: {
            type: "number",
            description: "Page number to retrieve",
            default: 1,
          },
          per_page: {
            type: "number",
            description: "Number of results per page (default: 20, max: 100)",
            default: 20,
          },
        },
      },
    };
  • index.ts:566-572 (registration)
    The tool is registered by including getMembersTool in the tools list returned by ListToolsRequest handler.
    case "esa_get_members": {
      const args = request.params.arguments as unknown as GetMembersArgs;
      const response = await esaClient.getMembers(args.page, args.per_page);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • EsaClient method implementing the core logic for fetching team members from ESA API with optional pagination.
    async getMembers(page?: number, per_page?: number): Promise<any> {
      const params = new URLSearchParams();
      
      if (page) params.append("page", page.toString());
      if (per_page) params.append("per_page", per_page.toString());
    
      const url = `${this.baseUrl}/members${params.toString() ? `?${params}` : ""}`;
      const response = await fetch(url, { headers: this.headers });
    
      return response.json();
    }
  • TypeScript interface defining input arguments for esa_get_members tool.
    interface GetMembersArgs {
      page?: number;
      per_page?: number;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get a list' which implies a read-only operation, but doesn't disclose behavioral traits such as pagination details (implied by parameters), rate limits, authentication needs, or what data is included in the list. The description is minimal and lacks critical operational context.

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, efficient sentence with zero waste, making it appropriately sized and front-loaded. However, it's overly concise to the point of under-specification, lacking necessary details for a tool with no annotations or output schema, which slightly reduces its effectiveness.

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?

Given the tool's complexity (a list operation with pagination), lack of annotations, and no output schema, the description is incomplete. It doesn't explain return values, error handling, or provide enough context for the agent to use it effectively. The minimal description fails to compensate for the missing structured data.

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 description coverage is 100%, so the schema fully documents the two parameters (page and per_page) with descriptions and defaults. The description adds no parameter semantics beyond what the schema provides, but since coverage is high, the baseline score of 3 is appropriate as the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get a list of team members' clearly states the action (get) and resource (team members), but it's vague about scope and doesn't distinguish from sibling tools like 'esa_get_member' (singular). It specifies 'list' which helps differentiate from the singular sibling, but lacks detail on what constitutes a team member or the context.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or compare with siblings like 'esa_get_member' for individual members or other list tools. The description offers no usage instructions, leaving the agent to infer based on tool names 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/kajirita2002/esa-mcp-server'

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