Skip to main content
Glama

Uwear

by ai.uwear
OverviewDiscussionsAdmin

Create Art Direction

author_art_direction

Queue the conversation for asynchronous ArtDirection authoring using Uwear's prompt system. Use save=true when the user wants to create, build, or save a reusable ArtDirection. Use save=false when the user explicitly wants an unsaved draft or brainstorming pass. This returns a job ID; call get_art_direction_authoring_job until status is done or failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional requested ArtDirection name
saveNoSet true when the user wants to create, build, or save a reusable ArtDirection. Set false when the user explicitly wants an unsaved draft or brainstorming pass.
sourcesNoSupported authoring sources such as text, public URLs, image URLs, uploaded files, or durable reference image attachments
user_textNoConversation text to compile into ArtDirection markdown
image_urlsNoDraft-only reference image URLs to analyze into the ArtDirection. For saved ArtDirections, first save/select assets and pass reference_image_attachments.
reference_image_attachmentsNoPersistent authoring references as asset IDs. Use for save=true so the user can iterate the ArtDirection later. These are not generation-time references.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / $defs / ArtDirectionAuthoringSourceInput
      Added value: +{
+  "properties": {
+    "image_url": {
+      "default": null,
+      "maxLength": 2048,
+      "type": "string"
+    },
+    "reference_image_attachment": {
+      "$ref": "#/$defs/ArtDirectionReferenceImage",
+      "default": null
+    },
+    "source_type": {
+      "$ref": "#/$defs/ArtDirectionAuthoringSourceType"
+    },
+    "text": {
+      "default": null,
+      "maxLength": 50000,
+      "type": "string"
+    },
+    "uploaded_file_id": {
+      "default": null,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "url": {
+      "default": null,
+      "maxLength": 2048,
+      "type": "string"
+    }
+  },
+  "required": [
+    "source_type"
+  ],
+  "type": "object"
+}
    • addedInput schema / $defs / ArtDirectionAuthoringSourceType
      Added value: +{
+  "enum": [
+    "text",
+    "image_url",
+    "reference_image_attachment",
+    "public_url",
+    "uploaded_file",
+    "website_crawl"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / sources
      Added value: +{
+  "description": "Supported authoring sources such as text, public URLs, image URLs, uploaded files, or durable reference image attachments",
+  "items": {
+    "$ref": "#/$defs/ArtDirectionAuthoringSourceInput"
+  },
+  "maxItems": 50,
+  "type": "array"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false (so it's a mutation) but say nothing about async behavior. The description fills that gap by stating the operation is asynchronous, returns a job ID, and requires polling. It also clarifies the draft vs saved outcome. No contradiction with annotations.

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 concise sentences that front-load the core purpose, then give the save guidance, and finish with the follow-up polling instruction. Every sentence earns its place with no 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 complete for an agent to invoke the tool correctly: it explains the async queue, the save flag semantics, and the required next step (polling). The schema covers parameter details, and the lack of an output schema is compensated by the explicit job ID mention. Minor omission: no mention of prerequisites or error handling, but not critical.

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 parameters are already documented. The description adds value by explaining the practical usage of the save parameter ('Use save=true when...') and by hinting at the sources and user_text as inputs to the prompt system. This goes beyond the schema's description.

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?

The description states a specific verb ('Queue') and resource ('conversation for asynchronous ArtDirection authoring'), and clearly distinguishes this from a synchronous creation by mentioning the job ID and polling. It differentiates from siblings like create_art_direction by emphasizing the async nature and the save/draft distinction.

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 explicitly instructs when to set save=true vs save=false, and directs the agent to poll get_art_direction_authoring_job until done. While it doesn't name sibling alternatives like create_art_direction, it provides actionable context for the tool's primary decision (save flag) and follow-up procedure.

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