Skip to main content
Glama
Sign In
gthumb-mcp

gthumb-mcp

by larsupb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_thumbnail

Retrieve a 128px normal or 512px large image thumbnail from gThumb’s shared freedesktop cache, generating it automatically when missing.

Instructions

Get an image's thumbnail (128px 'normal' or 512px 'large') from the shared freedesktop thumbnail cache used by gThumb, generating one if missing.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
sizeNolarge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the cache location, the standard sizes, and the side effect that a thumbnail may be generated if missing (a write to the cache). Permissions and failure modes are not covered.

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 well-formed sentence with the resource, source, size options, and generation behavior front-loaded; no filler.

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?

No output schema exists, so the description should say what is returned (a file path? raw bytes?) and it doesn't. Core invocation details for a 2-param tool are otherwise covered.

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?

Schema coverage is 0% and the schema has no enum on 'size', so the description's mapping of 'normal'→128px and 'large'→512px is genuinely additive and essential for correct invocation. The 'path' parameter is left to be inferred from its name.

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?

States a specific verb+resource ('Get an image's thumbnail') and identifies the source (the shared freedesktop thumbnail cache). It clearly sits apart from the sibling get_image/get_image_info, though it doesn't explicitly contrast with them.

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 word 'thumbnail' – an agent can infer this is the cheap preview path versus get_image – but there is no explicit when-to-use, when-not-to-use, or named alternative.

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