Skip to main content
Glama
Sign In

PigmentaLab

by io.pigmentalab
OverviewDiscussionsAdmin

Check if an image can be printed at a given size

inspect_image_for_print
Read-only

Answer the question a print shop asks every day: can this artwork be printed at N cm without looking bad? Reports real pixel size, the largest print height at 300 dpi (optimal) and 150 dpi (floor), whether it has transparency, rough ink coverage, and warnings. Read-only, runs on CPU, costs NO credits. Run this before upscaling or laying out a sheet — it often makes the paid tool unnecessary. Pass target_height_cm to get a straight yes/no for a specific size.

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

Input Schema

NameRequiredDescriptionDefault
imageNo
handleNo
image_urlNo
target_height_cmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / $defs
      Added value: +{
+  "OpenAIFile": {
+    "properties": {
+      "download_url": {
+        "type": "string"
+      },
+      "file_id": {
+        "type": "string"
+      },
+      "file_name": {
+        "type": "string"
+      },
+      "mime_type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "download_url",
+      "file_id"
+    ],
+    "title": "OpenAIFile",
+    "type": "object"
+  }
+}
    • addedInput schema / properties / image / $ref
      Added value: +"#/$defs/OpenAIFile"
    • removedInput schema / properties / image / anyOf
      Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / image / default
      Removed value: -null
    • removedInput schema / properties / image / title
      Removed value: -"Image"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description goes well beyond them: CPU execution, zero credit cost, and the exact contents of the report (pixel size, max print height at 300/150 dpi, transparency, ink coverage, warnings). It does not cover failure behavior for unreadable or unsupported files, which keeps it short of a 5.

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?

Front-loaded with the user-facing question, then the return contents, then cost/compute profile, then the when-to-use rule. Every sentence adds a distinct decision-relevant fact with no restatement of the title or name.

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 output schema, the description correctly spends words enumerating the returned fields, including the 300 dpi optimal and 150 dpi floor thresholds and warnings. The remaining gap is the unresolved choice among image, handle, and image_url inputs, which matters given all four parameters are optional.

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 coverage is 0%, so the description carries the full burden, and it only explains target_height_cm. The three interchangeable image-source parameters (image, handle, image_url) are never distinguished, so an agent cannot tell which one to populate or whether they are mutually exclusive.

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 concrete verb and resource framed as a real question ("can this artwork be printed at N cm without looking bad?") and names what it reports. It is unmistakably distinct from siblings like upscale_image and improve_image, which mutate or generate rather than measure.

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

Usage Guidelines5/5

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

"Run this before upscaling or laying out a sheet — it often makes the paid tool unnecessary" gives an explicit ordering and a routing rule away from the paid siblings. The conditional guidance for target_height_cm ("to get a straight yes/no for a specific size") tells the agent exactly when the optional parameter matters.

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

All PigmentaLab 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