Skip to main content
Glama
anoopt

Outlook Meetings Scheduler MCP Server

find-person

Locate email addresses by entering a person's name to streamline adding attendees in Microsoft Outlook meeting scheduling using the Microsoft Graph API.

Instructions

Find a person's email address by their name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName or partial name of the person to find

Implementation Reference

  • Registration of the 'find-person' tool using registerTool, including inline schema and handler.
      registerTool(
        server,
        "find-person",
        "Find a person's email address by their name",
        {
          name: z.string().describe("Name or partial name of the person to find"),
        },
        async ({ name }) => {
          const { graph, userEmail, authError } = await getGraphConfig();
    
          // Check for authentication errors
          if (authError) {
            return {
              content: [
                {
                  type: "text",
                  text: `🔐 Authentication Required\n\n${authError}\n\nPlease complete the authentication and try again.`,
                },
              ],
            };
          }
    
          // Search for the person by name
          const people = await graph.searchPeople(name, userEmail);
          
          if (!people) {
            return {
              content: [
                {
                  type: "text",
                  text: "Failed to search for people. Check the logs for details.",
                },
              ],
            };
          }
      
          if (people.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: `No people found matching "${name}". Please provide the full email address.`,
                },
              ],
            };
          }
      
          // Format the results for response
          const peopleList = people.map((person: any, index: number) => {
            const email = person.mail || person.userPrincipalName || person.emailAddresses?.[0]?.address || "No email available";
            const displayName = person.displayName || "Unknown name";
            return `${index + 1}. ${displayName} (${email})`;
          }).join("\n");
          
          const successMessage = `
    Found ${people.length} people matching "${name}":
    
    ${peopleList}
    
    You can use these email addresses to create a calendar event.`;
      
          return {
            content: [
              {
                type: "text",
                text: successMessage,
              },
            ],
          };
        }
      );
  • Input schema for the 'find-person' tool using Zod.
    {
      name: z.string().describe("Name or partial name of the person to find"),
    },
  • Handler function for 'find-person' tool: authenticates, searches for people by name using graph API, formats results.
        async ({ name }) => {
          const { graph, userEmail, authError } = await getGraphConfig();
    
          // Check for authentication errors
          if (authError) {
            return {
              content: [
                {
                  type: "text",
                  text: `🔐 Authentication Required\n\n${authError}\n\nPlease complete the authentication and try again.`,
                },
              ],
            };
          }
    
          // Search for the person by name
          const people = await graph.searchPeople(name, userEmail);
          
          if (!people) {
            return {
              content: [
                {
                  type: "text",
                  text: "Failed to search for people. Check the logs for details.",
                },
              ],
            };
          }
      
          if (people.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: `No people found matching "${name}". Please provide the full email address.`,
                },
              ],
            };
          }
      
          // Format the results for response
          const peopleList = people.map((person: any, index: number) => {
            const email = person.mail || person.userPrincipalName || person.emailAddresses?.[0]?.address || "No email available";
            const displayName = person.displayName || "Unknown name";
            return `${index + 1}. ${displayName} (${email})`;
          }).join("\n");
          
          const successMessage = `
    Found ${people.length} people matching "${name}":
    
    ${peopleList}
    
    You can use these email addresses to create a calendar event.`;
      
          return {
            content: [
              {
                type: "text",
                text: successMessage,
              },
            ],
          };
        }
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. The description only states what the tool does ('Find a person's email address'), but doesn't disclose important behavioral aspects like what happens when multiple matches are found, whether it's case-sensitive, what format the email address is returned in, or any error conditions. For a lookup tool with zero annotation coverage, this is a significant gap.

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 that directly states the tool's purpose. There's no wasted words or unnecessary elaboration. It's front-loaded with the essential information and doesn't include any extraneous details.

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 that there are no annotations and no output schema, the description is incomplete for effective tool usage. While it states what the tool does, it doesn't provide enough context about the behavior, return format, or error handling. For a lookup tool that presumably returns email addresses, the description should ideally specify what format the result comes in or what happens when no match is found.

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 the single parameter 'name' clearly documented as 'Name or partial name of the person to find'. The description adds minimal value beyond what's already in the schema - it mentions 'by their name' which is redundant with the parameter documentation. Since schema coverage is high, the baseline score of 3 is appropriate.

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 a person's email address by their name'. It specifies both the action ('Find') and the resource ('person's email address'), making it easy to understand what the tool does. However, it doesn't distinguish this tool from any potential sibling tools that might also involve finding people or email addresses, which prevents 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 any prerequisites, limitations, or suggest other tools for related tasks. While the sibling tools are all event-related (create, delete, get, list, update events), there's no explicit comparison or context provided for when to choose this person-finding tool over other methods.

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/anoopt/outlook-meetings-scheduler-mcp-server'

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