Skip to main content
Glama

Coline

Mark message important

set_message_priority
Idempotent

Marks one of the person's own messages important or urgent (people in the conversation are notified), or normal again.

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>",
      "priority": "<priority>"
    },
    "name": "set_message_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
priorityYes
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

A3.5/5.0
Behavior3/5

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

Annotations already declare it is a non-destructive, idempotent mutation, so the bar is lower. The description still earns credit for disclosing the side effect that conversation participants are notified, plus the own-message permission constraint; it does not say whether notification is re-sent on repeated calls despite idempotentHint, or what the response contains (an output schema exists).

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?

A single well-formed sentence with the side-effect parenthetical placed exactly where it matters, no filler. The only weakness is that the revert case ("or normal again") trails at the end instead of being stated as a first-class mode.

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

Completeness4/5

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

For a 5-parameter mutation tool with full annotations and an output schema, the description covers the what, the permission boundary, and the user-visible side effect. Remaining gaps (type/conversationId semantics, error behavior on non-owned messages) are modest given the schema and annotations carry that weight.

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?

The description enumerates the three priority values (normal, important, urgent), matching the enum in the schema. With 60% schema coverage it does not compensate for the undocumented parts: the "type" discriminator (channel/dm/task) and when conversationId is required are unmentioned, and the ownership rule for messageId is only implied.

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 (marks), resource (a message) and target state (important/urgent/normal), plus an ownership constraint ("one of the person's own messages") that separates it from sibling setters like set_priority_people or set_conversation_notifications. It never explicitly names an alternative tool, so it stops short of a 5.

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 purpose implies when to use it (marking a message important/urgent or reverting), and the ownership restriction rules out other people's messages. There is no explicit guidance on when to prefer this over adjacent actions such as pin_message or set_conversation_notifications, and no stated prerequisites or error conditions.

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