gthumb-mcp

Overview Schema Source Related Servers Discussions Admin

create_catalog

Creates a new, empty gThumb catalog at a given name or relative path (e.g., 'Random/Trips') so you can begin organizing images in a subfolder.

Instructions

Create a new, empty gThumb catalog. Use a relative path like 'Random/Trips' to place it in a subfolder.

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": "create_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.3/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. It discloses that the new catalog is empty and that the name supports a relative path, but it omits important mutation behavior: what happens if the catalog already exists, whether parent folders must already exist, permission requirements, and whether the operation is reversible.

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 tightly written sentences with no wasted words, and the core purpose is front-loaded before the path-format guidance.

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?

An output schema exists, so the description need not explain return values. However, for a mutation tool with no annotations, it is too thin on side effects, duplicate-name handling, and failure conditions to be fully self-sufficient.

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?

Schema description coverage is 0% for the single required "name" parameter, so the description must compensate. It adds useful meaning by clarifying that a relative path such as 'Random/Trips' can place the catalog in a subfolder, but it does not explain allowed characters, length constraints, or whether the name is also used as a display label.

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

Purpose4/5

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

The description gives a specific verb and resource ("Create a new, empty gThumb catalog"), which clearly distinguishes it from delete_catalog, list_catalogs, and add_to_catalog. It stops short of naming any sibling tool or explaining how it relates to those alternatives, so it does not reach the explicit differentiation required for a 5.

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?

Usage is implied by the tool name and the description: create a catalog when a new, empty catalog is needed. The description does not state when not to use it, prerequisites such as an existing gThumb library, or alternatives like add_to_catalog for adding images to an existing catalog.

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