Skip to main content
Glama

Coline

Save message for later

save_message

Saves a message to the person's Later list, with a state, a note or a reminder; or toggles it saved.

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

Input Schema

NameRequiredDescriptionDefault
noteNo
typeNo
stateNo
toggleNoSave it, or unsave it if it's saved.
remindAtNo
messageIdYesMessage id from read_conversation.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdNoFrom list_conversations.

Output Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, and the description adds real context beyond them: it names the target surface (the Later list) and discloses the toggle/unsave behavior, which is the main surprising side effect. It still omits what happens when state, note, remindAt, and toggle are combined, and whether re-saving is required or whether saving replaces earlier values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler; the core action comes first and the variants follow. It is dense to the point of ambiguity ("or toggles it saved", "with a state, a note or a reminder"), but nothing is redundant.

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?

An output schema exists, so return values need not be explained, and the description covers the core action adequately. For an 8-parameter mutation with 50% schema coverage, however, the definition leaves the interaction between parameters and the effect of the enum values unexplained, which is a meaningful gap at this complexity.

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 50%, so the description needs to carry some weight; it does partially by mapping to the state, note, and reminder parameters and by using "or" to suggest these are alternative modes. But it says nothing about the `type` enum (channel/dm/task), the meaning of the four state values, or whether remindAt requires a paired reminder, leaving half the parameters documented only by bare enums.

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

Purpose4/5

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

States a specific verb and resource ("Saves a message to the person's Later list") plus the optional payloads it accepts (state, note, reminder) and the toggle variant. That is enough to separate it from edit_message, pin_message, or delete_message without opening schemas, though it never names a sibling explicitly.

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?

Usage is only implied: the "Later list" framing tells an agent this is a save-for-later action, and "or toggles it saved" hints at the unsave path. There is no explicit when-to-use vs. when-not, no guidance on choosing toggle versus state, and no mention of prerequisites such as needing a messageId from read_conversation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources