mcp-hey

Overview Schema Source Related Servers Discussions Admin

hey_set_aside

Idempotent

Move an email thread to Set Aside for later review without replying. Reversible and returns a success status for emails you plan to revisit.

Instructions

Move an email thread to Set Aside for later. Reversible via hey_unset_aside (requires postingId from hey_list_set_aside). Returns {success, error?}. Use for emails you plan to revisit but don't need to reply to — for emails needing a reply, use hey_reply_later instead. Does not affect future emails from the sender.

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": {
      "id": "<id>"
    },
    "name": "hey_set_aside"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The topic or entry ID to set aside (use topicId or entryId from list operations)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.0May 9, 2026

removedInput schema / properties / entry_id

Removed value: -{
-  "description": "The entry ID to set aside (use entryId from list operations)",
-  "type": "string"
-}

addedInput schema / properties / id

Added value: +{
+  "description": "The topic or entry ID to set aside (use topicId or entryId from list operations)",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "entry_id"
-]New value: +[
+  "id"
+]

First observedv0.1.0May 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare it non-read-only, idempotent, and non-destructive; the description adds the operational details that matter: the action is reversible via hey_unset_aside, which requires a postingId obtained from hey_list_set_aside, the response shape is {success, error?}, and it does not affect future emails from the sender.

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?

Four compact sentences with the core action, reversibility, return shape, and routing rule front-loaded; no filler and nothing repeated from structured fields.

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

Completeness5/5

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

For a one-parameter mutation with no output schema, the description supplies the return shape, the undo path, and the side-effect boundary, leaving nothing an agent needs to invoke it correctly unstated.

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 coverage is 100% and the single parameter is already documented there (topicId/entryId). The description adds no syntax or format detail for the id beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb (Move) and resource (email thread) plus the destination state (Set Aside). It differentiates itself from siblings by naming hey_reply_later as the alternative for a different intent.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('emails you plan to revisit but don't need to reply to'), when-not ('emails needing a reply'), and the alternative tool (hey_reply_later). Also names the reversal path (hey_unset_aside) and the prerequisite ID source.

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