Skip to main content
Glama

Outlook List Tasks

outlook_list_tasks
Read-only

Lists Outlook tasks from the local profile, omitting completed items by default. Set include_completed to true to view finished tasks alongside open ones.

Instructions

List Outlook tasks. Completed tasks are omitted unless include_completed is true.

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": "outlook_list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_completedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds one genuinely useful behavioral fact — completed tasks are omitted by default — but says nothing about ordering, result limits, pagination, or scope of the returned task set.

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

Conciseness4/5

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

Two short sentences with the core action front-loaded and the filtering caveat immediately after; nothing is padded or redundant. It could be slightly sharper by naming the parameter inline as code, but the structure is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and a single optional boolean keeps the surface small. What remains thin is the scope of the listing (which account/mailbox, any result cap), which an agent might still need.

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 0%, so the description must carry the parameter meaning; it does explain that include_completed controls whether completed tasks appear. That is accurate but minimal, adding nothing about format, interaction with other filters, or what happens when combined with defaults beyond the stated one.

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 gives a specific verb and resource ("List Outlook tasks"), which is clearly distinct from the mail, calendar, and folder siblings. It stops short of explicitly contrasting itself with any alternative, so it earns a solid 4 rather than a 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?

There is no guidance on when to call this versus another tool, nor any prerequisites or scoping notes (e.g., which mailbox or account is queried). The only usage-adjacent information is the default exclusion of completed tasks, which is a behavior, not a selection rule.

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