Skip to main content
Glama
Sign In

Vitrine: Trending Fashion, Luxury, Sneakers & Design

by fashion.vitrine
OverviewDiscussionsAdmin

Item details

get_item
Read-onlyIdempotent

Get the full record for one item, using an id from a search, trending or find_similar result. Use it before recommending a piece, to check sizes, materials, colors, shipping regions and seller. With a key it adds silhouette, occasion, season and trend data. Returns {item, meta}. An unknown id returns an error result telling you to search again. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer ') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key. With a key, each item also carries trend_reason (why it has its trend status), trend_sources (the signals behind it: source, url, signal type, date, contribution; [] when the status comes from curation alone) and trend_review (when the status last changed and whether a human reviewer approved it).

Input Schema

NameRequiredDescriptionDefault
idYesItem id from a search, trending or find_similar result.
agentNo

Output Schema

NameRequiredDescriptionDefault
itemYes
metaYes
query_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / item / properties / gender
      Added value: +{
+  "description": "Department. Accessories and interior are usually unisex.",
+  "enum": [
+    "women",
+    "men",
+    "unisex"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "item": {
+      "properties": {
+        "availability": {
+          "enum": [
+            "in_stock",
+            "low_stock",
+            "preorder",
+            "out_of_stock"
+          ],
+          "type": "string"
+        },
+        "brand": {
+          "type": "string"
+        },
+        "category": {
+          "type": "string"
+        },
+        "colors": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "currency": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "image_url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "materials": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "outbound_url": {
+          "description": "Tracked link to the retailer's product page. Checkout happens there.",
+          "type": "string"
+        },
+        "price": {
+          "type": "number"
+        },
+        "ship_to": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "sizes": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "sold_by": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        },
+        "trend_score": {
+          "description": "0 to 100. With a key.",
+          "type": "integer"
+        },
+        "trend_status": {
+          "description": "With a key.",
+          "enum": [
+            "hot",
+            "rising",
+            "steady",
+            "fading"
+          ],
+          "type": "string"
+        },
+        "why": {
+          "description": "One-line reason it matches. With a key.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "title",
+        "brand",
+        "price",
+        "currency",
+        "availability",
+        "outbound_url"
+      ],
+      "type": "object"
+    },
+    "meta": {
+      "properties": {
+        "access": {
+          "enum": [
+            "full",
+            "basic"
+          ],
+          "type": "string"
+        },
+        "terms": {
+          "type": "string"
+        },
+        "upgrade": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "query_id": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "item",
+    "meta"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the anonymous result cap of 5 items, which fields are withheld without a key, how to obtain a key and pass it, and the exact rate limits (10/min anonymous, 60/min keyed). It also states the failure mode for an unknown id ('returns an error result telling you to search again').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentences are tightly front-loaded and earn their place, but the final sentence spends ~60 words enumerating trend_reason, trend_sources and trend_review fields, which duplicates the existing output schema. Rate limits and auth could also be compressed into one clause.

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 single-record lookup with an output schema present, everything an agent needs is covered: valid id provenance, expected envelope {item, meta}, auth path, quotas, gated fields and error behavior. Nothing material is left unspecified.

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 50% and the required 'id' parameter is already documented identically in the schema; the description repeats rather than extends it. The only added meaning is auth-related (Bearer key), which is not a parameter, and the optional 'agent' object is never discussed.

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?

States a specific verb and resource ('Get the full record for one item') and immediately scopes the input to ids from search, trending or find_similar, which separates it from those lookup siblings. An agent can distinguish it from search/trending without opening any schema.

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?

Gives a concrete when-to-use condition ('before recommending a piece, to check sizes, materials, colors, shipping regions and seller') and points to the sibling tools that produce valid ids. It stops short of an explicit when-not or a named alternative for the case where the agent has no id.

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

All Vitrine: Trending Fashion, Luxury, Sneakers & Design toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources