Skip to main content
Glama

Star, mute or archive a conversation

thread_set_flags
Idempotent

Stars (important), mutes (no email/Telegram) or archives one of your conversations. Only your own view changes; the Barmaan team is not notified.

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": {
      "thread": "<thread>"
    },
    "name": "thread_set_flags"
  }
}

Input Schema

NameRequiredDescriptionDefault
mutedNo
threadYesConversation reference (TH-…) from threads_list.
starredNo
archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), so the bar is lower. The description adds genuinely useful scope context: changes are private to the caller's view and no notifications are sent to the Barmaan team. It omits important behavioral details for a mutation tool, though — whether passing false clears a flag, whether omitted fields are left unchanged, and whether all three flags can be set in one call.

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?

Two sentences, zero filler, with the action and its three modes front-loaded before the side-effect clarification. Nothing in the text is redundant with the title or annotations.

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?

With annotations covering safety and idempotency and no output schema to explain, the description is close to sufficient for a simple flag-setting tool. It still leaves the agent guessing about the update model (partial vs. full replacement) and how to unset a flag, which is the main thing an agent would need beyond the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, with just the thread reference documented, so the description must carry the three booleans — and it does, giving a plain-language meaning for starred, muted, and archived. What it does not clarify is the semantics of an omitted or false boolean, which matters for a partial-update tool with additionalProperties=false. That gap keeps it below a 5 despite strong coverage of the flag meanings.

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?

The description names a specific resource (a conversation) and the exact operations it performs, defining each flag inline: starring as 'important', muting as 'no email/Telegram', archiving as removing it from view. This is far more specific than the title alone. It does not, however, differentiate itself from nearby siblings like thread_close or thread_mark_read, so an agent must infer that this tool toggles flags rather than changing thread lifecycle state.

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?

There is no when-to-use guidance: nothing says when to prefer this over thread_close or thread_mark_read, and no prerequisites are stated. The parenthetical definitions of the flags describe what each flag means rather than when an agent should set it. The only implied guidance is that this is the tool for star/mute/archive, which an agent could already infer from the title.

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