Skip to main content
Glama
Sign In
mcp-hey

mcp-hey

by Sealjay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

hey_reply_later

Idempotent

Move an email thread to Reply Later to defer a response you intend to send, not set aside. Reversible.

Instructions

Move an email thread to Reply Later. Reversible via hey_remove_reply_later (requires postingId from hey_list_reply_later). Returns {success, error?}. Use for emails you intend to respond to but not right now — if no reply is planned, use hey_set_aside instead.

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_reply_later"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe topic or entry ID to mark for reply later (use topicId or entryId from list operations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • removedInput schema / properties / entry_id
      Removed value: -{
-  "description": "The entry ID to mark for reply later (use entryId from list operations)",
-  "type": "string"
-}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "The topic or entry ID to mark for reply later (use topicId or entryId from list operations)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "entry_id"
-]New value: +[
+  "id"
+]
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a mutation (readOnlyHint=false), idempotent, and non-destructive; the description adds genuinely new context: reversibility via hey_remove_reply_later, the postingId prerequisite from hey_list_reply_later, and the return shape {success, error?}. It stops short of describing side effects like removal from the Imbox, which keeps it below a 5.

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?

Three short clauses: action, reversal path, decision rule with alternative. Front-loaded and every sentence earns its place with no padding.

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?

With no output schema, the description supplies the return shape, the undo path, and the routing rule against a sibling — everything an agent needs to call and recover from this tool correctly.

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% and the single 'id' parameter is documented there (topicId or entryId from list operations), so the baseline applies. The description's mention of postingId pertains to the reversal tool rather than the input, adding no new meaning about the argument itself.

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 and resource ('Move an email thread to Reply Later') and explicitly contrasts with siblings hey_set_aside and hey_remove_reply_later, so an agent can distinguish it without opening other schemas.

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 intend to respond to but not right now') and when-not-to-use with a named alternative ('if no reply is planned, use hey_set_aside instead'), plus the reversal path. Nothing is left to inference.

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