ccx_admin_list_nodesList database and load-balancer nodes for a datastore, showing hostname, IP, role, status, DB version, cloud instance type, and availability zone.
List the database and load-balancer nodes of a datastore: hostname, IP, role, cmon host status (e.g. CmonHostOnline), DB version, cloud instance id/type and availability zone.
| Name | Required | Description | Default |
|---|---|---|---|
| datastore_id | Yes | Datastore UUID |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds useful details about the returned fields and status values, but it does not disclose pagination, limits, error behavior, or other operational characteristics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that states the resource, scope, and returned fields without unnecessary words. It is easy to scan and gives an agent the essential information immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only list operation, the description covers the required identifier and the expected output contents. It omits minor operational details like pagination or result limits, but the combination of schema, annotations, and description is sufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter datastore_id is fully documented in the schema with its type, pattern, and description, and schema coverage is 100%. The description does not add parameter-specific guidance, but none is needed because the schema carries the full semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and identifies the exact resource: 'database and load-balancer nodes of a datastore'. It also enumerates the fields returned, making it clearly distinct from sibling tools like ccx_admin_list_datastores and ccx_admin_get_datastore.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description makes the use case clear: use it to list the nodes of a specific datastore. However, it does not explicitly mention alternatives or state when not to use the tool, so it lacks full exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.