Skip to main content
Glama

vibedeploy

by be.vibedeploy
OverviewDiscussionsAdmin

List snapshots for a site

list_snapshots
Read-onlyIdempotent

List the Longhorn volume snapshots for a site. Snapshots are point-in-time backups of the site's served files. Any team member can list snapshots. Returns NO_VOLUME if the site has no volume yet (it has never been deployed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
siteIdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
snapshotsYesLonghorn snapshot objects for the site's volume (name, created timestamp, size, etc.).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / request_id
      Removed value: -{
-  "description": "Server-assigned request correlation id. Quote it when contacting support.",
-  "type": "string"
-}
  2. Changed1 schema field changed
    • addedOutput schema / properties / request_id
      Added value: +{
+  "description": "Server-assigned request correlation id. Quote it when contacting support.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover readOnly, idempotent, and destructive hints; the description adds valuable behavioral context beyond those: the NO_VOLUME error condition for never-deployed sites and the permission note that any team member can list. This is rich, non-obvious behavioral disclosure.

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 tight sentences with the main action front-loaded. Every sentence adds useful content: scope, definition, permission, and an edge-case return value. No filler.

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

Completeness3/5

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

The description covers behavior and an important error case, and an output schema exists, so return values need no explanation. However, the two optional parameters remain underspecified, and the description does not resolve how an agent should select between name and siteId, leaving a meaningful gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the meaning of 'name' versus 'siteId'. The phrase 'for a site' hints at scope but does not clarify which parameter identifies the site or whether they are alternatives, leaving real ambiguity.

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 states a specific verb and resource: 'List the Longhorn volume snapshots for a site.' It clearly distinguishes the tool from sibling create_snapshot and other list_* tools by naming the resource type and scope.

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 provides clear context: snapshots are point-in-time backups, any team member can list them, and NO_VOLUME is returned for undeployed sites. It does not explicitly name alternatives or when-not-to-use scenarios, but the listing purpose is unambiguous.

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

All vibedeploy toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources