Skip to main content
Glama

esa_get_member

Retrieve team member details by screen name or email to identify contributors and access their information within the esa platform.

Instructions

Get information about a specific team member

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
screen_name_or_emailYesScreen name or email of the member to retrieve

Implementation Reference

  • Handler for the esa_get_member tool: validates input arguments and invokes the EsaClient.getMember method to fetch member data.
    case "esa_get_member": {
      const args = request.params.arguments as unknown as GetMemberArgs;
      if (!args.screen_name_or_email) {
        throw new Error("screen_name_or_email is required");
      }
      const response = await esaClient.getMember(args.screen_name_or_email);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • EsaClient method that performs the HTTP fetch to retrieve specific member information from the Esa API.
    async getMember(screen_name_or_email: string): Promise<any> {
      const url = `${this.baseUrl}/members/${screen_name_or_email}`;
      const response = await fetch(url, { headers: this.headers });
    
      return response.json();
    }
  • Tool definition including name, description, and input schema for validating esa_get_member arguments.
    const getMemberTool: Tool = {
      name: "esa_get_member",
      description: "Get information about a specific team member",
      inputSchema: {
        type: "object",
        properties: {
          screen_name_or_email: {
            type: "string",
            description: "Screen name or email of the member to retrieve",
          },
        },
        required: ["screen_name_or_email"],
      },
    };
  • TypeScript interface defining the expected arguments for the esa_get_member tool.
    interface GetMemberArgs {
      screen_name_or_email: string;
    }
  • index.ts:616-616 (registration)
    Registration of the esa_get_member tool in the list of available tools returned by ListToolsRequest.
    getMemberTool,
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't clarify authentication requirements, error handling, rate limits, or what specific information is returned. This leaves significant gaps for a tool with no output schema.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what information is returned about the member, how errors are handled, or any behavioral nuances. For a read operation with no structured output documentation, more context is needed.

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%, with the single parameter 'screen_name_or_email' well-documented in the schema. The description doesn't add any additional meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 verb ('Get') and resource ('information about a specific team member'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from its sibling 'esa_get_members', which retrieves multiple members rather than a specific one.

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 like 'esa_get_members' for listing all members or other sibling tools for different resources. It lacks context about prerequisites or typical use cases.

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