Skip to main content
Glama

update_my_away_message

Set the auto-reply clients see when they message the coach (e.g. on holiday). Omit text or send an empty string to turn it off. (confirm-gated: previews until confirm: true)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_my_away_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only state that this is a non-read-only, non-destructive, closed-world write. The description adds two important facts beyond that: the message is client-visible (a real side effect), and execution is confirm-gated with a preview until confirm: true. It does not state whether an existing message is overwritten or what the preview looks like, which keeps it from 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 sentences, each doing distinct work: what the tool does, how to turn it off, and the confirmation behavior. It is front-loaded with the purpose and contains no filler.

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 two-parameter mutation tool with no output schema, the description covers purpose, disable semantics, and the confirm workflow, which is enough to invoke it correctly. It could be stronger by clarifying overwrite behavior and what the preview returns, but nothing critical is missing.

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 coverage is only 50% (text is undocumented in the schema), but the description compensates by defining the meaning of an omitted or empty text value and by explaining the confirm-gating contract. It does not mention the 1000-character limit or any content restrictions, so some schema detail is left to the schema.

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 gives a specific verb and resource: "Set the auto-reply clients see when they message the coach," plus a concrete example ("on holiday"). It is clearly distinguishable from most siblings by resource, though it never explicitly contrasts with update_my_availability, which an agent might confuse it with.

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?

It explains how to disable the away message (omit text or send an empty string), which is useful operational guidance. However, it offers no when-to-use guidance relative to siblings such as update_my_availability, and no explicit exclusions or prerequisites.

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.