Skip to main content
Glama
Sign In
Outlook Assistant

Outlook Assistant

by titanzero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list-folders

View and organize your Outlook mail folders with options to show item counts and hierarchical structure for better email management.

Instructions

Lists mail folders in your Outlook account

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeItemCountsNoInclude counts of total and unread items
includeChildrenNoInclude child folders in hierarchy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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 the action but lacks details on permissions, rate limits, pagination, or return format. This is inadequate for a tool that likely returns a list of folders without further context.

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, clear sentence with zero wasted words. It is front-loaded with the core purpose and efficiently communicates the essential action without unnecessary elaboration.

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 annotations and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., folder names, IDs, hierarchy), behavioral traits like authentication needs, or error conditions. For a list operation with potential complexity, this leaves significant gaps.

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%, so the input schema fully documents the two optional parameters. The description adds no parameter-specific information beyond implying the tool lists folders, which aligns with the schema but doesn't provide extra semantic value. This 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 ('Lists') and resource ('mail folders in your Outlook account'), making the purpose immediately understandable. However, it doesn't differentiate this from potential sibling tools like 'list-emails' or 'list-events' beyond the resource type, 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. There are no mentions of prerequisites, context for usage, or comparisons to sibling tools like 'search-emails' or 'create-folder', leaving the agent without directional cues.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools