Skip to main content
Glama
Sign In
gthumb-mcp

gthumb-mcp

by larsupb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_image

Retrieve an image's full content for viewing, downscaled to a maximum pixel size, so you can inspect or analyze a library file without loading oversized data.

Instructions

Get an image's full content for viewing, downscaled to fit max_size pixels.

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_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
max_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the safety and behavior burden. It usefully discloses that the image is downscaled to fit max_size pixels and intended for viewing, but it omits return encoding, error behavior, file-format support, and whether access is read-only.

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 wasted words. It quickly communicates the action, the resource, and the sizing behavior.

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?

For a simple two-parameter read tool, the description gives the core operation and max_size behavior, but no output schema exists and the path semantics and return format are underspecified. It is minimally adequate, not fully complete.

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%, so the description must explain both parameters. It clarifies max_size as a pixel bound for downscaling, but the required path parameter is left undescribed in terms of acceptable formats, relative vs. absolute paths, or image lookup semantics.

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 states a specific verb and resource: get an image's full content. It adds scope with 'for viewing' and 'downscaled to fit max_size pixels,' distinguishing it from a metadata or thumbnail operation, though it does not name sibling tools such as get_thumbnail or get_image_info.

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?

'For viewing' implies the intended use case, and max_size gives a hint about output sizing, but the description never explicitly says when to choose this over get_thumbnail, get_image_info, or open_in_gthumb. Usage is therefore implied rather than fully guided.

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