Skip to main content
Glama

Add Garment View

mcp_add_garment_view
DestructiveIdempotent

A Clothing card dropped on another. The photo of from_garment_id becomes the back, side or detail view of garment_id, and from_garment_id leaves the board (deleted only when it is a fresh drop nothing else uses). Or a photo put in the brief's missing-photo slot: image_url instead of from_garment_id, nothing leaves the board. The board's draft brief is saved again when the view changes it. Returns the board (and brief); asking again answers status unchanged.

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": {
      "garment_id": "<garment_id>",
      "view": "<view>",
      "expected_revision": "<expected_revision>",
      "board_id": "<board_id>"
    },
    "name": "mcp_add_garment_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYesback, side, or detail (a close-up)
board_idYesThe open Shoot Board's board_id, from Open Shoot Board or your context.
image_urlNoinstead of from_garment_id: the stored photo (host file download URL, or the image_url mcp_upload_intake_photo returned)
garment_idYesthe board garment that gains the photo as a view
from_garment_idNothe board garment whose photo it is; it leaves the board
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. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses exactly what is destroyed and under what condition: from_garment_id leaves the board and is deleted 'only when it is a fresh drop nothing else uses,' while the image_url path leaves the board untouched. It also adds side effects (the draft brief is re-saved) and idempotent behavior ('asking again answers status unchanged'), which is exactly the extra context annotations cannot carry.

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?

Four sentences, front-loaded with the primary drop-on-garment scenario, and every sentence carries information (modes, deletion rule, brief save, return value). Phrasing is slightly telegraphic ('The photo of from_garment_id', 'the board's draft brief is saved again') which costs some readability but not content.

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?

For a mutation tool with no output schema, the description covers the return value ('Returns the board (and brief)'), the destructive semantics of the source garment, the brief-save side effect, and repeat-call behavior. Combined with the schema's expected_revision conflict documentation, an agent has what it needs to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all six parameters and the baseline is 3. The description adds real meaning on top: it explains that image_url and from_garment_id are mutually exclusive modes and that from_garment_id causes the source garment to leave the board, which the schema alone does not convey.

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 states a concrete effect: the photo of from_garment_id becomes the back/side/detail view of garment_id, with a second mode using image_url for the brief's missing-photo slot. An agent can tell what the tool accomplishes, though the framing as a UI gesture ('a Clothing card dropped on another') is less direct than a verb+resource statement, and no sibling is named.

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?

It clearly lays out two usage modes and the condition selecting each: use from_garment_id when dropping one garment card onto another, use image_url when filling the brief's missing-photo slot. It does not name alternatives such as add_chat_photos_to_board or mcp_upload_intake_photo for routing purposes, so it stops short of explicit when-not guidance.

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