Simple Inventory Management

get_image_upload_link

Creates a one-time upload link for an inventory item's photo or the company logo, valid for 15 minutes and for one upload. Best for full-size photos. Two ways to use it: (1) if you can run code and your sandbox can reach this server, POST the image file to the link as multipart/form-data with the field name "file" (for example: requests.post(link, files={"file": open(path, "rb")})); the response is JSON saying whether it worked. (2) Otherwise give the link to the user: opening it on a phone shows a page to take or choose a photo. If a POST fails with a network or proxy error, your sandbox is blocked from this domain, so fall back to giving the user the link (or to set_image_from_base64).

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>"
    },
    "name": "get_image_upload_link"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes	"item" to set an inventory item's photo (also pass inventoryItemId), or "logo" to set the company logo.
`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.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses link lifetime (15 minutes), single-use semantics, required multipart field name ("file"), that the POST response is JSON indicating success, and what the user sees when opening the link on a phone. It also documents the failure mode (proxy/domain blocking) and the recovery path, which is exactly the behavioral context an agent cannot infer elsewhere.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with purpose and validity window, then enumerates the two usage modes clearly with numbered paths. The inline Python snippet is long but earns its place by removing ambiguity about the multipart field name. Slightly verbose overall, but no sentence is filler.

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?

No output schema and no annotations exist, yet the description covers what the link is, how to consume it both programmatically and via a human, what the response looks like, and what to do on failure. For a two-parameter tool of this shape, nothing an agent needs in order to call it correctly 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?

Schema coverage is 100%, so both parameters are already fully documented in the schema, and the description largely restates the item-vs-logo target distinction. It adds a small amount of meaning (the photo belongs to an inventory item, the logo to the company, and that this is "best for full-size photos") but no syntax or constraint detail beyond the schema. Baseline 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 opens with a specific verb and resource: "Creates a one-time upload link for an inventory item's photo or the company logo." It names both targets and scopes the artifact (one-time, 15-minute), which is enough for an agent to distinguish it from the sibling setters set_image_from_base64 and set_image_from_url.

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 routing rules: path (1) for agents that can run code and reach the server, path (2) otherwise, plus a stated fallback ("If a POST fails with a network or proxy error ... fall back to giving the user the link (or to set_image_from_base64)"). It also names the alternative tool by name, so when-to-use and when-not are both covered.

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?