Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

active_sessions

Read-onlyIdempotent

List currently authenticated vCenter/ESXi sessions with user, login time, last active, and IP address. Attribute changes to specific people by pairing results with active tasks.

Instructions

[READ] Currently authenticated vCenter/ESXi sessions (who is logged in).

Returns the list envelope with a real total; each row has user_name, full_name, login_time, last_active, ip_address and a current flag for this skill's own session. Requires the Sessions privilege; low-privilege accounts get a single explanatory row instead of a traceback.

Use this to attribute a change to a person — pair it with active_tasks, which names the user who started each task. Read-only — terminating a session is not supported here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax session rows to return (None = all).
targetNovCenter/ESXi target from config (default if omitted).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / description
      Added value: +"Max session rows to return (None = all)."
    • addedInput schema / properties / target / description
      Added value: +"vCenter/ESXi target from config (default if omitted)."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "active_sessionsOutput",
-  "type": "object"
-}New value: +null
  2. Addedv1.6.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the response envelope with a real total, enumerates row fields, mentions the current-session flag, and describes privilege-dependent behavior (single explanatory row instead of a traceback). The read-only nature is consistently reinforced. No contradiction with readOnlyHint/idempotentHint/destructiveHint.

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 dense, purposeful sentences with no filler. The core purpose is front-loaded, followed by return shape, privilege caveat, use case, and limitation. Every sentence earns its place.

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

Completeness5/5

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

Despite lacking an output schema, the description covers the return format, key fields, privilege requirements, failure/fallback behavior, and a practical pairing with active_tasks. The low parameter count and full schema coverage mean nothing essential is missing for correct invocation.

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?

Schema description coverage is 100%, with both limit and target already well described in the schema. The description does not add extra parameter-level detail, so the baseline of 3 is appropriate.

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?

States a specific verb ('Returns') and resource ('currently authenticated vCenter/ESXi sessions'), and clarifies 'who is logged in'. The scope is unmistakable and distinct from sibling list tools, with the [READ] marker reinforcing intent.

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?

Explicitly says to use it 'to attribute a change to a person' and recommends pairing with active_tasks. It also notes that session termination is not supported, which is a clear exclusion. It could more explicitly contrast against read-only siblings, but the context is strong.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vmware-skills/VMware-Monitor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server