Skip to main content
Glama
Sign In
outlook-evidence-mcp

outlook-evidence-mcp

by ZachPackull
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get message

outlook_get_message

Retrieve a specific Outlook email's complete metadata and body for evidence collection, maintaining chain of custody.

Instructions

Fetch one message's full metadata + body (read-only).

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": {
      "messageId": "<messageId>"
    },
    "name": "outlook_get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'read-only', which indicates no side effects, but fails to disclose other behavioral traits such as authentication requirements, rate limits, or whether the operation is idempotent. For a fetch tool, more context is needed.

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, well-structured sentence with no wasted words. It efficiently conveys the core action and key property (read-only).

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 lacks details about return format, error handling, authentication prerequisites, and what 'full metadata' includes. For a simple tool, it is minimally adequate but leaves significant gaps.

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

Parameters2/5

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

Schema coverage is 0%, meaning the parameter 'messageId' has no description in the schema. The description adds minimal context by stating it fetches a message, implying messageId identifies which message, but does not specify format, source, or how to obtain it. This leaves ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('fetch'), the resource ('one message'), and the scope ('full metadata + body'), and explicitly marks it as read-only. It distinguishes itself from sibling tools like outlook_save_message (write) and outlook_search (search).

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?

The description implies usage for fetching a single message but does not provide explicit guidance on when to use this tool versus alternatives like outlook_search or outlook_list_attachments. No when-not-to-use or exclusions are given.

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