streetshirts

Add a border or keyline

add_keyline

Destructive

Apply a keyline to the explicit elementId and areaId. Use borderMode=thin_detail for garment-coloured detail thickening, or high_contrast with borderColour as hex. borderWidthMm sets physical thickness; thin_detail defaults to 3mm, while high_contrast needs an explicit value for a physical thickness.

Input Schema

Name	Required	Description
`options`	No	Existing 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.
`subject`	Yes	The exact subject returned by start_design_session.
`requestId`	Yes	Generate 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.
`sessionToken`	Yes	The private expiring capability returned by start_design_session. Do not publish it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / options / description

Previous value: -"Existing arguments; advanced fields/aliases remain accepted. Catalogue/session results include the full designArgumentSchema."New value: +"Existing 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."

Changed14 schema fields changedOct 14, 2026
- removedInput schema / properties / options / properties / backgroundColor
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / options / properties / backgroundRemovalMethod
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / options / properties / borderColour
```
Added value: +{
+  "description": "Hex colour for high_contrast, for example #ffffff; colour names are not supported.",
+  "type": "string"
+}
```
- addedInput schema / properties / options / properties / borderMode
```
Added value: +{
+  "description": "thin_detail uses the garment colour; high_contrast accepts an explicit borderColour.",
+  "enum": [
+    "thin_detail",
+    "high_contrast"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / options / properties / borderWidthMm
```
Added value: +{
+  "description": "Physical keyline thickness in millimetres. thin_detail defaults to 3; set explicitly for high_contrast.",
+  "type": "number"
+}
```
- removedInput schema / properties / options / properties / colorKeyHex
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / options / properties / colourKeyHex
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / options / properties / feather
```
Removed value: -{
-  "type": "integer"
-}
```
- removedInput schema / properties / options / properties / method
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / options / properties / paddingPx
```
Removed value: -{
-  "type": "integer"
-}
```
- removedInput schema / properties / options / properties / preserveImageBox
```
Removed value: -{
-  "type": "boolean"
-}
```
- removedInput schema / properties / options / properties / preserveReplacementBox
```
Removed value: -{
-  "type": "boolean"
-}
```
- removedInput schema / properties / options / properties / tolerance
```
Removed value: -{
-  "type": "integer"
-}
```
- removedInput schema / properties / options / properties / whiteBorder
```
Removed value: -{
-  "type": "boolean"
-}
```
First observedOct 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds meaningful behavioral detail about mode-dependent colour behavior and width defaults, though it does not itself explain the destructive overwrite risk noted in the schema.

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?

Three short sentences, front-loaded with the core action and followed by mode guidance. Every sentence carries useful information and there is no redundant filler.

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?

The description is sufficient for invoking the tool: it explains the target, the two border modes, colour format, and width behavior. Annotations and schema cover the destructive nature, nested options, session token privacy, and required fields, so only minor contextual gaps remain.

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%, so the schema already documents all parameters. The description reinforces borderMode and borderWidthMm semantics, especially the 3mm default and explicit-width requirement for high_contrast, but adds little beyond the schema's existing parameter descriptions.

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 specific verb and resource: apply a keyline to explicit elementId and areaId. It is clear what the tool does, but it does not differentiate this tool from any sibling or name an alternative border-related operation.

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?

It provides useful mode-selection guidance for thin_detail versus high_contrast, but it does not say when to use add_keyline versus other tools or when to avoid it. Usage is implied rather than explicitly scoped against alternatives.

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

All streetshirts tools Inspect

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

Need Help?