Skip to main content
Glama

Iminify

by com.iminify
OverviewDiscussionsAdmin

Get an image

get_image
Read-onlyIdempotent

One image with its status, sizes and savings. Poll this, a few seconds apart, until the status is completed, already-optimized, failed or cancelled. Once finished, optimized.download_url downloads the result and original.download_url the file as it was sent; both addresses work without a token and expire after an hour, so ask again for fresh ones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe image's id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe image's id.
hintNoWhat to do next, when the status alone does not say.
nameNoThe name the optimized copy downloads under.
statusNo
scan_idNoThe page scan that found it, if one did.
originalNo
settingsNo
optimizedNoNull until the image has finished.
share_urlNoIts public page, once shared.
created_atNo
updated_atNo
saved_bytesNoNegative when the optimized copy is larger.
saved_percentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "created_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hint": {
+      "description": "What to do next, when the status alone does not say.",
+      "type": "string"
+    },
+    "id": {
+      "description": "The image's id.",
+      "type": "string"
+    },
+    "name": {
+      "description": "The name the optimized copy downloads under.",
+      "type": "string"
+    },
+    "optimized": {
+      "description": "Null until the image has finished.",
+      "properties": {
+        "download_url": {
+          "description": "Works without a token for an hour.",
+          "type": "string"
+        },
+        "format": {
+          "type": "string"
+        },
+        "height": {
+          "type": "integer"
+        },
+        "name": {
+          "type": "string"
+        },
+        "size": {
+          "description": "Bytes.",
+          "type": "integer"
+        },
+        "width": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "name",
+        "format",
+        "size",
+        "width",
+        "height",
+        "download_url"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "original": {
+      "properties": {
+        "download_url": {
+          "description": "Works without a token for an hour.",
+          "type": "string"
+        },
+        "format": {
+          "type": "string"
+        },
+        "height": {
+          "type": "integer"
+        },
+        "name": {
+          "type": "string"
+        },
+        "size": {
+          "description": "Bytes.",
+          "type": "integer"
+        },
+        "width": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "name",
+        "format",
+        "size",
+        "width",
+        "height",
+        "download_url"
+      ],
+      "type": "object"
+    },
+    "saved_bytes": {
+      "description": "Negative when the optimized copy is larger.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "saved_percent": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "scan_id": {
+      "description": "The page scan that found it, if one did.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "settings": {
+      "properties": {
+        "height": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "keep_metadata": {
+          "type": "boolean"
+        },
+        "level": {
+          "enum": [
+            "none",
+            "lossless",
+            "ultra",
+            "smart",
+            null
+          ],
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "scale": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "width": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "level",
+        "keep_metadata",
+        "width",
+        "height",
+        "scale"
+      ],
+      "type": "object"
+    },
+    "share_url": {
+      "description": "Its public page, once shared.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "enum": [
+        "queued",
+        "optimizing",
+        "completed",
+        "failed",
+        "already-optimized",
+        "cancelled"
+      ],
+      "type": "string"
+    },
+    "updated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The annotation declares readOnlyHint and idempotentHint, and the description adds meaningful behavioral context beyond that: token-free download URLs, one-hour expiration, and the need to re-poll for fresh URLs. It also enumerates the exact terminal statuses an agent should wait for. This is exactly the kind of runtime behavior an agent needs to know.

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 three sentences, each earning its place: the first defines the return content, the second explains polling behavior, and the third covers download URLs and expiration. It is front-loaded with the core purpose and contains no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a single documented parameter and an output schema present, the description covers the essential operational details: polling, terminal states, download_url fields, authentication requirements, and expiry. An agent has everything needed to correctly invoke and interpret the result of this tool.

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?

The schema already provides 100% coverage for the single id parameter with a clear description. The tool description adds no additional meaning to the parameter itself, so the baseline of 3 is appropriate. There is nothing missing that the description would need to compensate for.

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?

The description states a specific verb-resource pair: it retrieves one image along with status, sizes, and savings. It clearly differentiates from list_images by emphasizing a single image and from get_scan by naming image-specific fields. The phrase 'One image' makes the scope immediately obvious.

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?

The description gives explicit guidance on when and how to use the tool: poll every few seconds until a terminal status is reached. It clearly defines the terminal statuses, which is strong usage context. It does not explicitly contrast this with sibling tools, but the polling lifecycle makes the intended usage unmistakable.

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

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