Simple Inventory Management

set_image_from_url

Sets an inventory item's photo or the company logo from an image on the web (for example a manufacturer's product photo). The server downloads the image itself, so nothing large passes through the conversation. Only public https:// addresses that return a JPEG, PNG, WebP, GIF or BMP image (up to 15 MB) work. For a photo the user pasted into the chat, use set_image_from_base64 or get_image_upload_link instead.

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": {
      "target": "<target>",
      "imageUrl": "<imageUrl>"
    },
    "name": "set_image_from_url"
  }
}

Input Schema

Name	Required	Description
`target`	Yes	"item" to set an inventory item's photo (also pass inventoryItemId), or "logo" to set the company logo.
`imageUrl`	Yes	The https:// address of the image file itself (not a web page that shows it).
`inventoryItemId`	No	The inventory item id when target is "item" (from get_inventory).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it discloses important behavior: the server downloads the image itself, large data does not pass through the conversation, and only public https URLs returning supported image formats up to 15 MB work. It does not state authentication or permission requirements, nor whether an existing image is overwritten.

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 front-loaded with the core action and resource, then adds the key constraint and the alternative in three efficient sentences. Every sentence adds useful information without repetition.

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?

For a three-parameter mutation with complete schema coverage and no output schema, the description covers the action, source constraints, supported formats, size limit, and alternative tools. The only notable omissions are auth/overwrite behavior, which are minor but relevant for a mutation tool without annotations.

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 the meanings of target, imageUrl, and inventoryItemId are already documented in the input schema. The description adds useful context by restricting imageUrl to a direct public https image file and by mentioning the item/logo targets, but it adds no new per-parameter syntax or behavior beyond the schema. With complete schema coverage, the baseline score of 3 is appropriate.

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 uses a specific verb, "Sets," and clearly names the resources: an inventory item's photo or the company logo. It also distinguishes this tool from the image-paste alternatives by explaining that the image comes from the web.

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 explicitly says to use this when the image is on the web, such as a manufacturer's product photo, and when not: for a photo the user pasted into chat, use set_image_from_base64 or get_image_upload_link. This is clear routing to the correct sibling tool.

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

All Simple Inventory Management tools Inspect

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

Need Help?