Skip to main content
Glama

hypsh fashion stylist

by com.hypsh
OverviewDiscussionsAdmin

Search fashion products

semantic_search
Read-onlyIdempotent

Use this when the user wants to find specific fashion products (clothing, footwear, accessories) by text, optionally guided by images. Pass gender when you know who the clothes are for. Do not use this for full outfit generation or visualization-only requests. The result's content is a plain-text list of the products (brand, price); structuredContent.products holds the same products with ids and shop links.

Input Schema

NameRequiredDescriptionDefault
queryYes
genderNoWho the clothes are for: 'female' or 'male'. Set it whenever the user says or the conversation suggests it ('for my boyfriend', 'women's', a gender they mentioned earlier, the kind of piece they ask for). Only ask the user if there is no hint at all and the answer would clearly differ by gender. Omit for unisex requests.
imagesNo
countryNoISO 3166-1 alpha-2 code of the country the shopper is in (e.g. 'DE', 'US'), if known. Used to show shops that deliver there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 3166-1 alpha-2 code of the country the shopper is in (e.g. 'DE', 'US'), if known. Used to show shops that deliver there."
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by explaining the return shape: `content` is a plain-text list and `structuredContent.products` holds ids and shop links. It does not mention rate limits, result caps, or how image-guided search behaves, which keeps it below a 5.

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 tight sentences, front-loaded with the usage condition followed by exclusions and return-shape detail. Every sentence adds decision-relevant information without repetition.

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?

With no output schema, the description appropriately explains the return format (`content` and `structuredContent.products`), which is important for downstream use. It covers the critical gaps for a read-only search tool, though it could say more about image input expectations and result limits.

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 50%; `gender` and `country` are richly documented in the schema, while `query` and `images` are not. The description adds some value for `images` by saying results can be 'optionally guided by images,' and it reinforces when to pass `gender`, but it does not explain image format, count limits, or query syntax. That is adequate but not compensating fully for the undocumented parameters.

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 ('find specific fashion products (clothing, footwear, accessories) by text, optionally guided by images') and distinguishes itself from outfit generation and visualization-only tools. An agent can immediately tell what this tool does and how it differs from the sibling `generate_outfit`.

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?

Provides explicit usage conditions ('Use this when the user wants to find specific fashion products...') and explicit exclusions ('Do not use this for full outfit generation or visualization-only requests'), which routes the agent away from `generate_outfit`. The additional guidance on when to pass `gender` further reduces ambiguity.

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

All hypsh fashion stylist 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