Skip to main content
Glama

List stack data assets

list_stack_data_assets
Read-only

List what data a stack actually holds (the twin of ankra cluster stacks data list): standalone persistent volume claims and database custom resources with their claims folded in, each with engine, consistency, requested size and storage class. custom_resource_scan says whether the live database-operator read ran - unavailable means the database list is incomplete, not that there are no databases. Read-only. Only offered when backups are enabled for the organisation.

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": {
      "stack_name": "<stack_name>"
    },
    "name": "list_stack_data_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the cluster. Alternative to cluster_name.
stack_nameYesThe stack to inventory.
cluster_nameNoExact name of the cluster. Optional when a cluster is already selected in the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses meaningful runtime semantics: the custom_resource_scan field indicates whether the live database-operator read succeeded, and 'unavailable' means the database list is incomplete rather than empty. That prevents a costly false conclusion about a stack having no databases. It repeats 'Read-only', which the annotation already covers, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and returned fields, then the important empty-vs-incomplete caveat, then constraints. The CLI-twin parenthetical is mild noise but aids agents familiar with the underlying command; overall dense with little waste.

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?

With no output schema, the description does the work of outlining the returned attributes and the scan-status caveat, and it flags the backups-enabled gating condition. What remains unsaid is the choice between cluster_id and cluster_name at call time, which the schema covers adequately.

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%, so all three parameters (stack_name, cluster_id, cluster_name) are already documented in the schema, including the alternative/optional relationship between cluster identifiers. The description adds only that the tool is stack-scoped, not any new parameter meaning. Baseline 3 applies.

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+resource (list the data a stack holds) and enumerates exactly what is returned: standalone PVCs and database custom resources with claims folded in, plus engine, consistency, requested size and storage class. This distinguishes it from sibling listers like get_pvcs or describe_resources, which are generic Kubernetes reads rather than a stack-scoped data inventory.

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

Usage Guidelines3/5

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

The description gives an availability precondition ('Only offered when backups are enabled for the organisation') and a reading caveat, but never says when to prefer this over alternatives such as get_pvcs or describe_resources. Usage is implied by the 'what data a stack actually holds' framing rather than stated as an explicit routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.