Skip to main content
Glama

userDetails

Retrieve comprehensive contact details by providing an email address using this tool. Ideal for managing and analyzing user information on the Mailmodo platform.

Instructions

Tool to get all details of a contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes

Implementation Reference

  • Core handler function that performs the API call to retrieve contact details from Mailmodo using the provided email.
    export async function getContactDetails(
        mmApiKey: string,
        email: string
    ): Promise<any | null> {
        if (!email) {
            throw new Error('Email is a required field');
        }
    
        try {
            const response = await axios.get<any>(
                `https://api.mailmodo.com/api/v1/getContactDetails?email=${encodeURIComponent(email)}`,
                {
                    headers: {
                        'Accept': 'application/json',
                        'mmApiKey': mmApiKey || ''
                    }
                }
            );
    
            return response.data;
        } catch (error) {
            if (error instanceof AxiosError) {
                return null;
            }
            throw new Error('An unexpected error occurred');
        }
    }
  • Input schema for the userDetails tool, defining the required 'email' parameter as a string.
    {
      email: z.string(),
    },
  • src/server.ts:62-76 (registration)
    Registration of the 'userDetails' MCP tool, including description, schema, and inline handler that delegates to getContactDetails and formats the response.
    server.tool(
      "userDetails",
      "Tool to get all details of a contact ",
      {
        email: z.string(),
      },
      async ({ email }) => {
        const details = await getContactDetails(mmApiKey,email);
        return{
        content: [{
          type: "text",
          text: JSON.stringify(details)
        }]
      }}
    );
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. While 'get' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or what 'all details' includes (e.g., contact fields, timestamps). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise—a single sentence with no wasted words. It's front-loaded with the core purpose, making it easy to parse. Every word earns its place by directly contributing to understanding the tool's function.

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 simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't explain the parameter, expected output format, or behavioral constraints. While concise, it lacks necessary details for effective use, especially with zero schema description coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter (email) with 0% description coverage, meaning the schema provides no semantic context. The description doesn't mention the email parameter at all, failing to compensate for the schema's lack of documentation. It should explain what the email parameter represents (e.g., the contact's email address to look up).

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: 'get all details of a contact' specifies both the verb ('get') and the resource ('contact details'). It distinguishes itself from siblings like addContactToList or archiveContact by focusing on retrieval rather than modification. However, it doesn't explicitly differentiate from potential read-only siblings that might exist.

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, context for usage, or compare it to sibling tools like MailmodoCampainReportTool or sendEvent. The agent must infer usage solely from the purpose statement.

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

Related 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/mailmodo/mailmodo-mcp'

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