Skip to main content
Glama

aptly_list_snapshots

List all snapshots in Aptly repositories to manage and track Debian package versions effectively.

Instructions

List all snapshots

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List all snapshots' implies a read-only operation, but it doesn't specify details like pagination, sorting, error conditions, or output format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise with 'List all snapshots', consisting of just three words. It's front-loaded and wastes no space, making it efficient for an agent to parse. Every word earns its place by specifying the action and resource.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a list operation. It doesn't explain what 'snapshots' are in this context, how results are returned, or any limitations. For a tool in a server with multiple list operations, more context is needed to distinguish it fully.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't add parameter information, which is unnecessary here. With no parameters, the baseline is 4, as there's nothing to compensate for, and the description doesn't detract from this.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all snapshots' clearly states the verb ('List') and resource ('snapshots'), making the purpose understandable. However, it lacks specificity about scope or format, and doesn't differentiate from sibling tools like 'aptly_list_mirrors' or 'aptly_list_repos' beyond the resource name. This makes it adequate but vague.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, such as how it relates to 'aptly_create_snapshot' or 'aptly_publish_snapshot'. Without any usage context, the agent must infer based on the name alone.

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

Related 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/rashidazarang/aptly-mcp'

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