Charlotte

charlotte_screenshot_delete

Delete a screenshot artifact by ID to remove the file from disk.

Instructions

Delete a saved screenshot artifact by its ID. Removes the file from disk.

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": {
      "id": "<id>"
    },
    "name": "charlotte_screenshot_delete"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Screenshot artifact ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.8.0Aug 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedv0.6.3May 26, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosing side effects. It explicitly states 'Removes the file from disk,' which conveys the destructive, persistent nature of the operation. It does not detail error handling or permissions, but for a simple delete operation, this is substantial 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?

The description is two short sentences, front-loads the core action, and contains no filler or repetition. Every word contributes meaning.

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?

For a simple deletion tool with one parameter and no output schema, the description adequately covers the action and its effect. It does not mention how to obtain the ID or that the deletion is permanent, but the essentials are present, and the simplicity of the tool reduces the need for further context.

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?

The input schema already has 100% coverage, documenting the single 'id' parameter as 'Screenshot artifact ID to delete.' The description adds little beyond restating 'by its ID,' so the schema carries the semantic weight. This matches the baseline for high schema coverage.

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 uses a specific verb ('Delete') and clearly identifies the resource ('saved screenshot artifact') and the required identifier ('by its ID'). It is unambiguous and distinguishes this tool from sibling tools like charlotte_screenshot_get, which retrieves rather than deletes.

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 implies when to use the tool—when a saved screenshot artifact needs to be deleted—but gives no explicit guidance about when not to use it or alternatives. It does not mention that this is the only tool for deletion or that retrieval tools should be used for other purposes.

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