Skip to main content
Glama
Sign In
SnapStack Server

SnapStack Server

by bgaze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Clear screenshots

clear_screenshots

Delete pending screenshots from the stack. Pass specific capture numbers to remove, or omit to clear all screenshots and reset numbering.

Instructions

Delete pending screenshots from the stack. Pass "numbers" to delete only specific captures (e.g. [1] or [2,3]); omit to clear the whole stack. Once the stack is empty, numbering restarts at 01.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_screenshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
numbersNoCapture numbers to delete (e.g. [2,3]). Omit to clear all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Without annotations, the description provides behavioral details like the numbering restart after stack clears. It explains the optional parameter behavior but does not mention any other side effects.

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 two concise sentences with no wasted words. The first sentence states the purpose; the second adds key usage details.

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 simple tool with one optional parameter and no output schema, the description covers behavior, parameter usage, and an edge case (numbering restart). It is fully adequate.

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 description adds value beyond the schema by explaining the parameter's effect (delete specific captures) and the default behavior (omit to clear all).

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 clearly states the action (delete) and resource (pending screenshots from the stack). It distinguishes from siblings count_screenshots and get_screenshots by focusing on deletion.

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?

The description explains when to use the tool (to delete screenshots) and how to specify numbers or clear all. It implicitly differentiates from siblings but does not explicitly state when not to use it.

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

Deploy Server

Other Tools