Skip to main content
Glama
vmware-skills

vmware-vdi

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

session_send_message

Send informational messages to VMware Horizon sessions, targeting by session IDs or user, to notify users about maintenance or other updates without disrupting sessions.

Instructions

[WRITE] Send a message to Horizon session(s) — e.g. "save your work, maintenance in 10 min".

Low blast radius (informational only, no session disruption), so no confirm gate. Identify by session_ids OR user. Audited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoMessage all sessions of this AD user (substring match).
targetNoHorizon target from config.yaml; omit to use the default.
messageYesThe text to display to the user(s).
session_idsNoSession ids to message.
message_typeNoINFO, WARNING, or ERROR.INFO

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / message / description
      Added value: +"The text to display to the user(s)."
    • addedInput schema / properties / message_type / description
      Added value: +"INFO, WARNING, or ERROR."
    • addedInput schema / properties / session_ids / description
      Added value: +"Session ids to message."
    • addedInput schema / properties / target / description
      Added value: +"Horizon target from config.yaml; omit to use the default."
    • addedInput schema / properties / user / description
      Added value: +"Message all sessions of this AD user (substring match)."
  2. First observedv1.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations, the description adds meaningful behavioral context: "low blast radius", "informational only, no session disruption", "no confirm gate", and "Audited." These details are not inferable from readOnlyHint=false and destructiveHint=false alone.

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 description is compact and front-loaded: the action, an example, risk level, targeting rule, and audit note all fit in three short sentences. Every sentence earns its place with no fluff or repetition of the schema.

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 write operation with 100% schema coverage and no output schema, the description covers the important behavioral context: how to identify recipients, why confirmation is not needed, and why this is safe. It does not mention response behavior, but that is largely unnecessary for a message-sending tool and the schema already documents all parameters.

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 100%, so the baseline is 3. The description adds value on top by clarifying the targeting relationship between session_ids and user, and reinforces the message text semantics with an example. This lifts it slightly above baseline.

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

Purpose5/5

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

The description begins with a specific verb+resource pattern: "Send a message to Horizon session(s)" and includes a concrete example message. It also distinguishes itself from disruptive sibling actions like session_logoff or session_disconnect by explicitly labeling this as informational-only.

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?

It clearly states how to target sessions via "session_ids OR user", provides a realistic use case, and explains that no confirm gate is needed. It does not explicitly enumerate when not to use this tool versus alternatives like session_logoff, but the informational framing makes the intended usage clear.

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

Deploy Server

Other Tools