Skip to main content
Glama
Sign In
mailnotmilk

mailnotmilk

by jrb00013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_thread

Fetch the complete conversation thread for a specific message ID, providing full context without searching through individual emails.

Instructions

Fetch the full conversation thread for a message id.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for disclosing behavior. It only states 'Fetch', implying a read-only operation, but does not mention any side effects, auth requirements, or whether the thread includes ordering or pagination. No contradictions exist, but the information is insufficient.

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 concise sentence, front-loaded with the verb 'Fetch'. It contains no fluff and efficiently communicates the core purpose.

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 the lack of annotations and output schema, the description is too sparse. It does not mention what the returned thread looks like, how it is ordered, or any limitations. The tool has two parameters, but the description only hints at one, leaving the context incomplete.

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 must compensate. It explicitly mentions 'message id' which maps to the 'message_id' parameter, but it does not explain the 'limit' parameter at all. The description adds minimal value over the schema.

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 action ('Fetch') and the resource ('full conversation thread for a message id'). It is specific and distinguishes from siblings like 'read_message' or 'chat_history' by focusing on the entire thread for a given message ID.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparisons to similar tools like 'chat_history' or 'read_message'.

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