Skip to main content
Glama
Meerkats-Ai

Hatch MCP Server

by Meerkats-Ai

hatch_find_email

Find email addresses by entering a person's first name, last name, and company domain to locate professional contact information.

Instructions

Find an email address using first name, last name, and domain information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstNameYesFirst name of the person
lastNameYesLast name of the person
domainYesCompany domain name

Implementation Reference

  • Handler for the 'hatch_find_email' tool. Validates input parameters using the isFindEmailParams type guard, makes a POST request to the Hatch API endpoint '/v1/findEmail' with retry logic, and returns the JSON response or an error message.
    case 'hatch_find_email': {
      if (!isFindEmailParams(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid arguments for hatch_find_email'
        );
      }
    
      try {
        const response = await withRetry(
          async () => apiClient.post('/v1/findEmail', args),
          'find email'
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
          isError: false,
        };
      } catch (error) {
        const errorMessage = axios.isAxiosError(error)
          ? `API Error: ${error.response?.data?.message || error.message}`
          : `Error: ${error instanceof Error ? error.message : String(error)}`;
    
        return {
          content: [{ type: 'text', text: errorMessage }],
          isError: true,
        };
      }
    }
  • Tool schema definition for 'hatch_find_email', including name, description, and input schema specifying required firstName, lastName, and domain parameters.
    const FIND_EMAIL_TOOL: Tool = {
      name: 'hatch_find_email',
      description: 'Find an email address using first name, last name, and domain information.',
      inputSchema: {
        type: 'object',
        properties: {
          firstName: {
            type: 'string',
            description: 'First name of the person',
          },
          lastName: {
            type: 'string',
            description: 'Last name of the person',
          },
          domain: {
            type: 'string',
            description: 'Company domain name',
          },
        },
        required: ['firstName', 'lastName', 'domain'],
      },
    };
  • Type guard function isFindEmailParams used to validate input arguments for the hatch_find_email handler.
    function isFindEmailParams(args: unknown): args is FindEmailParams {
      return (
        typeof args === 'object' &&
        args !== null &&
        'firstName' in args &&
        typeof (args as { firstName: unknown }).firstName === 'string' &&
        'lastName' in args &&
        typeof (args as { lastName: unknown }).lastName === 'string' &&
        'domain' in args &&
        typeof (args as { domain: unknown }).domain === 'string'
      );
    }
  • TypeScript interface defining the input parameters for hatch_find_email.
    interface FindEmailParams {
      firstName: string;
      lastName: string;
      domain: string;
  • src/index.ts:312-320 (registration)
    Registration of tools list handler, which includes FIND_EMAIL_TOOL in the response to list tools requests.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        FIND_EMAIL_TOOL,
        FIND_PHONE_TOOL,
        VERIFY_EMAIL_TOOL,
        FIND_COMPANY_DATA_TOOL,
        GET_LINKEDIN_URL_TOOL,
      ],
    }));
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 'Find[s] an email address' but doesn't describe how it works (e.g., guessing patterns, querying a database), what happens on failures, rate limits, or authentication needs. This is inadequate for a tool with no 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 that directly states the tool's purpose and required inputs. It's front-loaded with essential information and has no wasted words, making it easy for an agent to parse quickly.

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 moderate complexity (3 required parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and inputs but lacks details on behavior, output format, or error handling. Without annotations or output schema, more context would be helpful for reliable use.

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 schema description coverage is 100%, with clear descriptions for each parameter (e.g., 'First name of the person'). The description adds no additional semantic context beyond what the schema provides, such as format examples or constraints. This meets the baseline of 3 when schema coverage is high.

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: 'Find an email address using first name, last name, and domain information.' It specifies the verb ('Find'), resource ('email address'), and required inputs. However, it doesn't explicitly differentiate from sibling tools like hatch_find_phone or hatch_verify_email, which prevents a score of 5.

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 sibling tools like hatch_verify_email (for verification) or hatch_find_phone (for phone numbers), nor does it specify prerequisites or exclusions. This leaves the agent without context for tool selection.

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/Meerkats-Ai/hatch-mcp-server'

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