Skip to main content
Glama
Sign In

ThumbnailMaker

by so.thumbnailmaker
OverviewDiscussionsAdmin

Correct a thumbnail

correct_thumbnail

Changes one thing on an existing thumbnail by instruction ("make the text bigger", "warmer light"); the rest of the image stays put and the original is kept. One thumbnail (10 credits). First call without confirm to get the price. Studio plan.

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": {
      "thumbnailId": "<thumbnailId>",
      "instruction": "<instruction>"
    },
    "name": "correct_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoLeave out on the first call to get the price. Send true only after the person agreed to it.
quoteIdNoThe quoteId the price call returned; required with confirm: true.
instructionYesOne change, e.g. "make the text bigger"
thumbnailIdYesThe id returned by generate_thumbnail or list_thumbnails

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the rest of the image stays unchanged, the original is preserved, cost is one thumbnail (10 credits), and it is a plan-gated paid operation requiring a quote-then-confirm flow. This goes well beyond the readOnly/destructive/idempotent hints.

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?

Two tight sentences plus a short cost/plan tag; the operative constraint (one change, rest stays put, original kept) is front-loaded with no wasted prose.

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?

No output schema exists, and the description covers the key workflow, preservation semantics, cost, and plan gate, which is enough for correct invocation. It stops short of stating what the corrected result returns (e.g., a new thumbnail id versus in-place update), leaving a small gap.

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 100%, so confirm/quoteId/instruction/thumbnailId are already documented. The description reinforces the quote-then-confirm sequencing and the 'one change' constraint on instruction, but adds little syntax or format detail beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb+resource (change one thing on an existing thumbnail) with a concrete mechanism and example instructions. It is clearly distinguishable from generate_thumbnail (new image) and check_thumbnail, since it operates on an existing thumbnail preserving the rest.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes the two-step invocation: first call without confirm to get the price, then confirm after the person agrees. It also states the Studio plan requirement. It does not name sibling alternatives (e.g., when to prefer generate_thumbnail instead), so it falls short of a 5.

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

All ThumbnailMaker toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources