gthumb-mcp

Overview Schema Source Related Servers Discussions Admin

delete_catalog

Deletes a gThumb catalog (.catalog) or saved-search (.search) file by name, removing unwanted collections from your photo library so you can keep library data organized and clutter-free.

Instructions

Delete a gThumb catalog (.catalog) or saved-search (.search) file.

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

Input Schema

Name	Required	Description	Default
`name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

B3.1/5.0

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. It states that deletion occurs, but does not say whether deletion is permanent or reversible, what permissions are required, what happens to catalog contents or referenced images, or whether confirmation is expected.

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 a single front-loaded sentence with no filler. Every element, the delete action and the two file types, contributes to identifying the tool.

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?

Although the tool has only one parameter and an output schema, it is destructive and has no annotations, so the description should cover irreversibility, permissions, or parameter format. As written, essential operational context for safely invoking a delete tool is missing.

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 only parameter is named simply "Name". The description does not clarify whether this is a catalog display name, filename with extension, or full path, leaving the required argument ambiguous.

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 resource ("a gThumb catalog (.catalog) or saved-search (.search) file"), and the file-type detail clearly distinguishes it from siblings such as create_catalog, add_to_catalog, and remove_from_catalog.

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?

It implies when deletion applies by naming catalog and saved-search files, but gives no explicit when-to-use guidance or alternatives. It does not clarify why an agent should choose this over remove_from_catalog, which affects catalog contents rather than deleting the catalog file itself.

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