Skip to main content
Glama

Uwear

by ai.uwear
OverviewDiscussionsAdmin

Analyze Image

view_image
Read-onlyIdempotent

Analyze any image using AI vision for manual inspection, debugging, visual description, or supplemental critique. Provide exactly one source: attachment_type together with attachment_id for a workspace record, generation_result_id for a Shoot Board generation, uploaded_file_id for a Files item, or image_url for a public HTTPS image. Do not use this as the primary QA mechanism when the user asks to QA, quality-check, validate, review, approve/reject, or assess generated results; for QA requests use queue_generation_result_qa first, then read_generation_result_qa.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesWhat to analyze: e.g. 'Is this a flat lay or worn on a model?', 'Does this need background removal?', 'Describe the garment details'. Do not use this as the primary tool for generation-result QA; use queue_generation_result_qa and read_generation_result_qa for QA requests.
image_urlNoPublic HTTPS image URL to analyze. Optional if generation_result_id or uploaded_file_id is provided.
attachment_idNoID of the workspace record to view. Supply together with attachment_type.
attachment_typeNoType of an attached workspace record. Supply together with attachment_id, without another image source.
uploaded_file_idNoID of an uploaded file to analyze. Use for items from the Files library.
generation_result_idNoID of an existing generation result to analyze. Preferred for Shoot Board generation items because the server resolves the HTTPS image URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / attachment_id
      Added value: +{
+  "default": null,
+  "description": "ID of the workspace record to view. Supply together with attachment_type.",
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / attachment_type
      Added value: +{
+  "default": null,
+  "description": "Type of an attached workspace record. Supply together with attachment_id, without another image source.",
+  "enum": [
+    "uploaded_file",
+    "generation_result",
+    "clothing_item",
+    "outfit"
+  ],
+  "type": "string"
+}
  2. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / generation_result_id / minimum
      Added value: +1
    • addedInput schema / properties / question / maxLength
      Added value: +4000
    • addedInput schema / properties / question / minLength
      Added value: +1
    • addedInput schema / properties / uploaded_file_id / minimum
      Added value: +1
  3. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds some useful context like the exactly-one-source constraint and that generation_result_id lets the server resolve the HTTPS image URL, but it does not add significant behavioral detail beyond what annotations and schema already convey.

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 tightly packed sentences front-load the purpose, then give the source constraint, then provide the critical QA exclusion. There is no fluff or repetition of schema details.

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 covers purpose, source selection, and QA routing thoroughly, and the schema documents all six parameters well. However, since there is no output schema, the description does not state what the tool returns (e.g., a textual answer), which is a minor completeness gap for an AI-vision tool.

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 baseline is 3. The description adds meaningful value by explaining the mutual exclusivity of image sources and why generation_result_id is preferred for Shoot Board generation items. This goes beyond the individual schema field descriptions.

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 opens with a specific verb and resource: 'Analyze any image using AI vision,' followed by concrete use cases (manual inspection, debugging, visual description, supplemental critique). It clearly distinguishes the tool from QA siblings by explicitly excluding QA workflows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance and names the alternatives for QA requests: queue_generation_result_qa first, then read_generation_result_qa. It also clearly states the 'exactly one source' exclusivity rule, which prevents ambiguous calls.

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