Skip to main content
Glama
Sign In
outlook-bridge

outlook-bridge

by PhamHoang16
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_thread

Retrieve all emails in a conversation thread by mail ID, sorted from oldest to newest, to view full context of a discussion.

Instructions

Lấy toàn bộ mail trong cùng luồng hội thoại, sắp từ cũ tới mới.

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": {
      "mail_id": "<mail_id>"
    },
    "name": "get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
mail_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses the sorting order (old to new) and the scope ('all emails in the thread'). However, it does not explain how the 'limit' parameter interacts with 'toàn bộ' (all), nor does it mention pagination, auth, or response shape.

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 focused sentence with no filler. It front-loads the primary action and scope, and the sorting detail adds useful information without bloating the text.

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

Completeness3/5

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

This is a relatively simple two-parameter tool with an output schema, so the description does not need to detail return values. Still, the meaning of 'limit', the potential conflict with 'all', and the absence of any usage boundaries leave a few gaps that an agent would have to infer.

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 description coverage is 0%, so the description needs to clarify parameters, but it never mentions mail_id or limit. The phrase 'same conversation thread' indirectly implies the role of mail_id, but no direct mapping or additional meaning is provided for either parameter.

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 states a specific verb ('get') and a well-defined resource ('all emails in the same conversation thread'), and clarifies the ordering (old to new). This distinguishes it from siblings like read_mail, which targets a single message, and search_mail, which searches across mail.

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 the use case: you call this when you need the full thread associated with a mail, rather than one individual message. However, it does not explicitly name alternatives or say when not to use it, so the guidance remains implicit rather than prescriptive.

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