Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

list_attachments

Read-onlyIdempotent

List an email's attachments by archive id or Message-ID, showing each file's name, type, size, and whether it is stored on this Mac; optionally include inline images.

Instructions

List an email's attachments: name, type, size, and whether the file is on this Mac.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email_id": "<email_id>"
    },
    "name": "list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesArchive id or Internet Message-ID of the email
include_inlineNoAlso list small inline images such as signature logos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so safety is covered. The description adds genuinely useful behavioral context by disclosing that results include a local-presence flag (the file may not be on this Mac). It says nothing about result ordering, pagination, or how inline images are surfaced beyond the schema's default.

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?

One short sentence, front-loaded with the action and followed by the returned fields; nothing is padded. It could be marginally tighter by folding the field list into a purpose-plus-return split, but there is no wasted wording.

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?

For a two-parameter read-only tool with full schema coverage and annotations but no output schema, the description covers the essentials and usefully spells out what each result contains. The only remaining gap is routing guidance to sibling tools, which is minor given the low complexity.

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%, including the meaning of email_id (archive id or Message-ID) and the include_inline default, so the schema does the heavy lifting. The description contributes no additional parameter meaning, which is the expected baseline here.

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 names a specific verb and resource ("List an email's attachments") and enumerates the fields returned, which makes the operation immediately distinguishable from the sibling get_attachment. It stops short of explicitly contrasting itself with that sibling, but the verb choice carries the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the fact that it lists rather than fetches content, plus the note about whether the file is on this Mac, suggests it as a discovery step before get_attachment. There is no explicit when-to-use statement, no exclusion of alternatives, and no guidance on pairing it with a download/fetch tool.

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