Skip to main content
Glama

outlook_list_emails

Retrieve a list of emails from your Microsoft Outlook inbox and other folders.

Instructions

List emails from Microsoft Outlook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:106-110 (registration)
    The tool 'outlook_list_emails' is registered in a loop over the TOOLS array. Line 45 defines it with description 'List emails from Microsoft Outlook' and line 107 registers it via server.tool(). The handler is a stub that returns an inspection message rather than real logic.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
  • The handler for 'outlook_list_emails' is a stub async function that returns a static message. The real implementation lives in a separate native binary (mentioned in the file header).
    server.tool(name, desc, {}, async () => ({
      content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
    }));
  • The schema for 'outlook_list_emails' is an empty object {} passed as the third argument to server.tool(), meaning no input parameters are defined.
    server.tool(name, desc, {}, async () => ({
Behavior1/5

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

With no annotations and a minimal description, the tool's behavioral traits are undisclosed. 'List' implies read-only, but there is no mention of scope, filtering, pagination, or output format, leaving the agent unaware of critical behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but under-informative. Every word should add value; here, it provides only basic purpose without additional context, so it is not fully efficient.

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 no output schema and no annotations, the description should explain what kind of emails are listed (e.g., from Inbox, recent, all). It lacks this context, making it incomplete for effective use.

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

Parameters4/5

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

The input schema has no parameters, and schema description coverage is 100%. The description adds no parameter details, but baseline for 0 parameters is 4, and it does not contradict the schema.

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 states 'List emails from Microsoft Outlook', specifying a clear verb (list) and resource (emails from Outlook). It distinguishes the tool from siblings like outlook_search_emails, but does not differentiate from a generic list_emails sibling, which could cause confusion.

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 on when to use this tool versus alternatives such as outlook_search_emails or list_emails. The description provides no context or exclusions, failing to help the agent decide.

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/lanchuske/local-mcp-releases'

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