Skip to main content
Glama

Agent message

user_message
Read-onlyIdempotent

Shows a short tray message to report milestones, completion summaries, questions, or blockers to the PC owner, with an optional one-click Open button for a result page, file, or folder.

Instructions

Show a short message to the PC owner in the tray (banner in the panel + icon tooltip; kind=request also pops a toast). PROACTIVELY call this to report key milestones, completion summaries, or questions/blockers — the PC owner watches the tray window directly. Display-only: nothing leaves the PC and nothing is executed. Pass open to hand over a result: the banner gets an Open button for that page, file or folder. Pass agent to identify yourself when multiple agents work in parallel. An empty text clears it.

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": {
      "text": "<text>"
    },
    "name": "user_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
kindNo
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
openNoOptional http(s) URL or local path (file or folder) the owner can open with one click from the message, e.g. a built page, a report or an output folder. Nothing opens automatically; programs and scripts are only shown in Explorer.
textYes
agentNoShort consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel.
persistentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, but the description adds genuinely new behavior: display-only with nothing leaving the PC, kind=request additionally popping a toast, and an empty text clearing the existing message. It leaves the effect of `persistent` and the meaning of `id` (the handle used to update or clear a message) undisclosed.

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?

The surface and the proactive call-to-action are front-loaded, then optional parameters are covered in short, purposeful clauses with no filler. Parentheses are used for concrete rendering detail rather than padding.

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 7-parameter, no-output-schema tool, the description covers visuals, safety profile, proactive usage, and most optional parameters well. It would be complete with a note on what `persistent` changes and what identifier is returned or reused to update/clear an existing message.

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 43%, so the description must carry weight, and it does: it explains `open` (an Open button for a page/file/folder, nothing auto-opens), `agent` (identify yourself when multiple agents run in parallel), `kind` (request also pops a toast) and `text` (empty clears the message). Only `id` and `persistent` receive no semantic treatment, which is a modest remaining gap.

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 ('Show a short message to the PC owner in the tray') and even describes the rendering surfaces (banner in the panel + icon tooltip). It is clear on its own, but it never distinguishes itself from the similarly named sibling 'agent_message', which an agent must choose between.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance: 'PROACTIVELY call this to report key milestones, completion summaries, or questions/blockers', plus the follow-up actions of passing `open` for a handover result. It stops short of when-not-to-use or naming alternatives (e.g. a sibling for agent-to-agent messaging or for waiting on an owner reply).

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