Skip to main content
Glama

Confirm an artwork upload

order_confirm_artwork_upload
Destructive

Step 2 of attaching artwork: report the completed PUT to register the file.

Call after PUTting the bytes to the presigned url. object_key is the one order_request_artwork_upload returned; size is the byte count you PUT. The filename and content type are the ones you presigned with. Marks the line covered, clears the payment refusal, and arms prepress, so the order can then reach page mapping and a payment link. Refused with ItemDesignAttachedError when the item of a multi-item order already holds an attached design, which is what prints.

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": {
      "session_id": "<session_id>",
      "order_id": "<order_id>",
      "item_id": "<item_id>",
      "size": "<size>",
      "object_key": "<object_key>"
    },
    "name": "order_confirm_artwork_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
item_idYes
order_idYes
object_keyYes
session_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false; the description usefully adds the downstream state transitions (marks the line covered, clears the payment refusal, arms prepress) and the error type raised on refusal. It does not explain the destructive aspect the annotation warns about (whether an existing attachment is replaced) nor what a retry does to a confirmed upload, leaving two annotation flags unelaborated.

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?

Front-loads the step number and core action, then sequences prerequisite, effects and error in a logical order with no filler sentences. The closing clause 'which is what prints' is slightly cryptic and could be tighter, but nothing is wasted.

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?

An output schema exists, so return values need not be described, and the description covers the sequencing, side effects and the main error case for a multi-step, destructive mutation. Gaps remain around retry/idempotency behavior and the full parameter set, which keeps it below a 5.

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 0% across five required parameters, so the description must compensate; it meaningfully explains only object_key (returned by order_request_artwork_upload) and size (the byte count PUT), leaving session_id, order_id and item_id to inference. It also references a 'url' and 'presigned' filename/content type that are not parameters of this call, which adds minor ambiguity.

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?

Names a specific verb and resource ('report the completed PUT to register the file') and explicitly positions itself as 'Step 2 of attaching artwork', which cleanly separates it from the step-1 sibling order_request_artwork_upload that it cites by name.

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?

Gives a concrete precondition ('Call after PUTting the bytes to the presigned url') and an explicit failure condition ('Refused with ItemDesignAttachedError when the item of a multi-item order already holds an attached design'). It stops short of stating when not to use it or naming an alternative recovery path after refusal, so it is a strong 4 rather than a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources