Skip to main content
Glama
vmware-skills

vmware-avi

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

pool_members

Read-onlyIdempotent

List all members of a specific pool, returning their IP, port, enabled state, and ratio. Use before enabling or disabling members to verify current configuration.

Instructions

[READ] List the members of a pool.

Returns Server IP, Port, Enabled and Ratio per member. Use before pool_member_enable or pool_member_disable; run pool_list first for the pool name. Reports configured state only, not live health-monitor results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolYesExact pool name as shown by pool_list — matched literally, not fuzzily, and an unknown name is refused rather than ignored. Pools are often named differently from the Virtual Services that use them, so do not infer it from a VS name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.8.14
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / pool / description
      Added value: +"Exact pool name as shown by pool_list — matched literally, not fuzzily, and an unknown name is refused rather than ignored. Pools are often named differently from the Virtual Services that use them, so do not infer it from a VS name."
  2. Addedv1.8.8
  3. Removedv1.8.8
  4. Addedv1.5.29
  5. Removedv1.5.28
  6. First observedv1.5.22

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds a valuable behavioral caveat: it reflects configured state, not live health-monitor results. It also discloses exactly which output fields are returned. No contradiction with the annotations exists.

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 and result fields come first, followed by workflow context and a caveat. Every sentence earns its place, with no filler or repeated schema information.

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?

For a read-only, single-parameter listing tool with an output schema, the description fully covers what it returns, prerequisites, sibling-tool relationships, and an important limitation. Nothing an agent needs to decide when or how to call it is missing.

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 coverage is 100%, and the pool parameter is already richly documented in the schema with exact-match semantics, literal matching, and a warning not to infer the pool name from a Virtual Service name. The description only reinforces this by saying to run pool_list first, so it adds little beyond the schema.

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?

Description starts with a clear action and object: 'List the members of a pool.' It also names the specific returned fields (Server IP, Port, Enabled, Ratio), and the '[READ]' prefix reinforces its read-only nature. The tool is distinguished from siblings by explicitly positioning it relative to pool_member_enable/pool_member_disable and pool_list.

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

Usage Guidelines5/5

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

It gives explicit workflow guidance: 'Use before pool_member_enable or pool_member_disable' and 'run pool_list first for the pool name.' It also states an exclusion — 'Reports configured state only, not live health-monitor results' — so an agent knows when not to rely on this tool.

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