Skip to main content
Glama
Sign In

Hoplix Print on Demand

by com.hoplix
OverviewDiscussionsAdmin

Check an image upload

get_design_upload
Read-onlyIdempotent

Status of a design upload: waiting_for_upload, uploaded (with file name, type, width and height in pixels) or expired.

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": {
      "design_upload_id": "<design_upload_id>"
    },
    "name": "get_design_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_upload_idYesUPL-... id of the upload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral detail by naming the possible status values and noting that the uploaded state includes file name, type, width, and height.

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 a single, front-loaded sentence that communicates the tool's purpose and return states without unnecessary wording.

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 simple read-only status tool with one fully documented parameter and no output schema, the description provides sufficient context by explaining the possible statuses and uploaded-file metadata. Minor gaps, such as error or expiry behavior, are not critical here.

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 single parameter, design_upload_id, is fully described in the schema as a UPL-... id. The description does not add further meaning beyond the schema, so the baseline of 3 is appropriate for full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that this tool reports the status of a design upload and lists the possible outcomes: waiting_for_upload, uploaded, or expired. It is specific about the resource and return states, though it does not explicitly distinguish itself from related siblings such as request_design_upload.

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

Usage Guidelines3/5

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

Usage is implied: call this to check the status of an existing design upload. However, the description does not explicitly say when to use this versus request_design_upload or what to do if the upload is expired or not found.

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

All Hoplix Print on Demand 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