Skip to main content
Glama
Sign In

streetshirts

by com.streetshirts
OverviewDiscussionsAdmin

Remove an image shape

remove_image_mask
Destructive

Remove the exact image's shape mask, including after saving and reopening. Restores its pre-mask proportions at the current placement and scale, retaining its Crop, filters and background treatment. Pass elementId and areaId.

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": {
      "subject": "<subject>",
      "sessionToken": "<sessionToken>",
      "requestId": "<requestId>"
    },
    "name": "remove_image_mask"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoExisting arguments; advanced fields/aliases remain accepted. Supplied design patches can overwrite session content; preview/rendering can fetch public image URLs in those designs. Catalogue/session results include the full designArgumentSchema.
subjectYesThe exact subject returned by start_design_session.
requestIdYesGenerate a UUID for a new action. Reuse it only for retrying/polling that same action and payload. A new user edit needs a new UUID.
sessionTokenYesThe private expiring capability returned by start_design_session. Do not publish it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=false, and openWorld=true, and the description adds real value on top: the change persists across save/reopen, pre-mask proportions are restored at the current placement and scale, and Crop, filters, and background treatment are retained. What it omits is failure behavior, e.g. what happens when the target has no mask.

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?

Three short sentences, front-loaded with the operation and followed by the resulting state and the required inputs. No filler, though "including after saving and reopening" is slightly awkward phrasing that could be tightened.

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 destructive single-element mutation with no output schema, the description covers what changes and what is preserved, while the session/subject/requestId parameters are fully documented in the schema. The main remaining gap is error/no-op behavior when no mask exists.

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 the baseline is 3. The description identifies elementId and areaId as the targeting inputs, which is mildly useful guidance the schema does not state, but it says nothing about the semantics of areaId (which print area the element sits on) and ignores elementIds and instruction.

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?

"Remove the exact image's shape mask" gives a specific verb plus resource and clearly implies the inverse of the sibling set_image_mask, so an agent can distinguish it from delete_element or restore_original_image. It stops short of naming the sibling outright, which keeps it from a 5.

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 by the operation itself, and "Pass elementId and areaId" points at the identifying inputs, but the description never states when to choose this over set_image_mask (to swap a mask) or restore_original_image (to revert all edits). No conditions, exclusions, or prerequisites are given.

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

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