Iminify

Create an upload link

create_upload_link

Get a one-time address to send a local file to, for an agent that can run a shell. PUT the file's bytes to upload_url (the answer includes a curl command), then call compress_images with the upload_id. The link expires after a few minutes and works once; the uploaded file keeps for about a day. Ask for one link per file. Uploads not yet compressed never outnumber the images the plan can still compress today, and never more than a fixed number of them: past that, a new link is refused with uploads_waiting, naming the upload ids already sent: compress those, then ask again.

Input Schema

Name	Required	Description	Default
`file_name`	Yes	The file's name, like "hero.png". It names the image; the extension is corrected to what the bytes turn out to be.

Output Schema

Name	Required	Description
`curl`	No	A command that sends the file.
`next`	No
`method`	No
`upload_id`	No	The id to pass to compress_images in upload_ids once the file is sent.
`expires_at`	No
`upload_url`	No
`max_file_size`	No	Bytes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "curl": {
+      "description": "A command that sends the file.",
+      "type": "string"
+    },
+    "expires_at": {
+      "type": "string"
+    },
+    "max_file_size": {
+      "description": "Bytes.",
+      "type": "integer"
+    },
+    "method": {
+      "enum": [
+        "PUT"
+      ],
+      "type": "string"
+    },
+    "next": {
+      "type": "string"
+    },
+    "upload_id": {
+      "description": "The id to pass to compress_images in upload_ids once the file is sent.",
+      "type": "string"
+    },
+    "upload_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: the link expires after a few minutes, works once, the uploaded file keeps for about a day, and there is a quota/backpressure condition that returns uploads_waiting. These details let an agent plan retries and cleanup correctly, even though annotations already mark this as a non-destructive creation tool.

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 purpose and immediate workflow are front-loaded, and each subsequent sentence adds operational detail about expiry, one-time use, per-file linking, or quota behavior. There is no wasted prose, and the density is appropriate for a tool with non-obvious upload constraints.

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 an output schema present, the description need not explain return values, and it still covers the key operational context: how to upload, when to compress, expiry, retention, and backpressure. Nothing essential for correct invocation is missing.

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?

There is only one parameter and schema description coverage is 100%, so the schema already defines file_name and its extension-correction behavior. The description adds workflow context but not parameter-level meaning beyond what the schema provides, making 3 the appropriate baseline.

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 and resource: get a one-time address to send a local file to, for an agent that can run a shell. It clearly distinguishes this tool from siblings by naming compress_images as the follow-up step, so an agent can recognize the upload-link workflow without opening the schema.

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?

It gives explicit usage steps: PUT the file's bytes to upload_url, then call compress_images with the upload_id, and it states one link per file. It also describes the refusal condition when too many uploads are waiting, telling the agent to compress those and ask again. This is strong when-to-use and when-not/retry guidance.

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

All Iminify tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?