Skip to main content
Glama
Sign In
gthumb-mcp

gthumb-mcp

by larsupb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_catalogs

Lists all gThumb catalogs and saved searches with their item counts, so you can identify available collections and see how many images each contains.

Instructions

List all gThumb catalogs and saved searches with their item counts.

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": "list_catalogs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden; 'List' reasonably implies a non-mutating read, and it discloses that item counts are included. It does not state ordering, pagination, or whether empty catalogs are returned, which leaves behavioral gaps for an unannotated tool.

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?

One front-loaded sentence with no filler; the resource and the returned attribute are stated immediately.

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?

With no parameters and an output schema present, return-value detail is not needed, and the description adequately frames the result set (catalogs plus saved searches with counts). Minor gaps around ordering/empties keep it from a 5.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description adds or contradicts parameter meaning.

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?

Specific verb (List) plus precise resource (gThumb catalogs and saved searches) with what is returned (item counts). Distinguishable from siblings get_catalog (single catalog) and list_tags (tags, not catalogs) without opening any schema.

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 verb — call it to enumerate catalogs — but there is no explicit statement of when to prefer it over get_catalog or which sibling to use for a single catalog's contents. For a zero-parameter read tool this inference is easy, so 3 rather than 2.

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