Skip to main content
Glama

Uwear

by ai.uwear
OverviewDiscussionsAdmin

Save Dropped Photos

mcp_commit_intake
Idempotent

Save sorted Shoot Board photos to the library as garments, avatars, locations or reference files, skip ones already saved, and add them to the Shoot Board at expected_revision; a board that changed is refused before anything is saved (revision_conflict with the current board).

Input Schema

NameRequiredDescriptionDefault
itemsYesPhotos to save, each with its confirmed kind
board_idYesThe open Shoot Board's board_id, from Open Shoot Board or your context.
expected_revisionYesBoard revision this write is based on; a stale revision returns a revision_conflict error with the current board instead of overwriting it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / items / items / properties / back
      Added value: +{
+  "description": "A new garment only: another photo of the same garment, showing its back (saved as its back photo; not with side back)",
+  "properties": {
+    "image_url": {
+      "description": "Public HTTP(S) URL of the uploaded image (host file download URL, or the image_url mcp_upload_intake_photo returned)",
+      "type": "string"
+    },
+    "sha256": {
+      "description": "Hex SHA-256 of the file bytes, computed by the widget",
+      "pattern": "^[0-9a-fA-F]{64}$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "image_url",
+    "sha256"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / items / items / properties / views
      Added value: +{
+  "description": "A new garment only: its other photos (full back or side once each, not with back; details any view, repeatable; not with side back)",
+  "items": {
+    "properties": {
+      "asset_kind": {
+        "enum": [
+          "full",
+          "detail"
+        ],
+        "type": "string"
+      },
+      "asset_view": {
+        "enum": [
+          "front",
+          "back",
+          "side",
+          "unspecified"
+        ],
+        "type": "string"
+      },
+      "image_url": {
+        "description": "Public HTTP(S) URL of the uploaded image (host file download URL, or the image_url mcp_upload_intake_photo returned)",
+        "type": "string"
+      },
+      "sha256": {
+        "description": "Hex SHA-256 of the file bytes, computed by the widget",
+        "pattern": "^[0-9a-fA-F]{64}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "image_url",
+      "sha256",
+      "asset_kind",
+      "asset_view"
+    ],
+    "type": "object"
+  },
+  "maxItems": 12,
+  "type": "array"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / side
      Added value: +{
+  "description": "A new garment only: the side its photo shows (default front; back: it is also its back photo)",
+  "enum": [
+    "front",
+    "back"
+  ],
+  "type": "string"
+}
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations cover the safety profile (non-read-only, non-destructive, idempotent), and the description adds real behavioral context beyond them: dedup by already-saved state, optimistic concurrency via expected_revision, and the atomic guarantee that a stale board is refused before anything is saved with a revision_conflict payload. That is exactly the write-failure semantics an agent needs before invoking.

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?

One front-loaded sentence that leads with the action, then the dedup rule, then the concurrency clause. The semicolon-chained clauses are dense but each carries information; nothing is padding.

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?

There is no output schema, and the description still discloses the failure shape (revision_conflict with the current board) and the atomicity guarantee, which is the main uncertainty for a batch write against a versioned board. Required inputs and their roles are otherwise fully documented in the schema.

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%, including detailed per-field docs for items, sha256, views and side, so the schema carries the load. The description only restates expected_revision's conflict behavior (already in the schema) and adds no syntax or format detail of its own; baseline 3 applies.

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?

States a specific verb and resource: it saves sorted Shoot Board photos into the library as one of four asset kinds, then attaches them to the board. The batch/dedup/revision-check framing implicitly separates it from single-asset siblings like mcp_upload_intake_photo and upload_garment_from_public_url, though it never names an alternative explicitly.

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?

The description places the tool in a clear workflow (photos are already sorted and screenshotted/uploaded; this commits them), and notes that already-saved photos are skipped rather than erroring. It gives no explicit exclusion such as 'use upload_garment_from_public_url for a single non-board garment', so guidance is clear but not complete.

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

All Uwear 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