Skip to main content
Glama

Aari Clothing — Premium Menswear, Activewear & Footwear

Render product detail

render_product_detail

Render the interactive detail UI for one exact Aari Clothing product. Pass a product_id when known; otherwise pass the exact product-name query directly because this tool resolves it internally. Use this only when the shopper explicitly asks to view, inspect, review, or get specifications for one exact product, or selects a product from search results. Do not call it automatically to rank, compare, validate, or explain discovery results. Do not call product search first to resolve the product. For matching items, recommended pairs or what to wear with this product, use render_complete_the_look instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_product_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
selectedNo
product_idNo
buyer_contextNo

Output Schema

NameRequiredDescriptionDefault
typeNoproduct_detail_result
storeYes
messageYes
productYes
selectedNo
sizeGuideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that the tool renders an interactive client UI and internally resolves a product name, but says nothing about what happens on zero or multiple matches, whether resolution costs time, or whether the render is idempotent across repeated calls.

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

Conciseness4/5

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

Front-loaded with the action and input precedence before the when/when-not rules, and every sentence blocks a specific failure mode (auto-calling, pre-searching, wrong sibling). Slightly long, but no sentence is filler; the 'view, inspect, review, get specifications' list is the only mild padding.

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?

An output schema exists, so return values need no explanation, and the routing, exclusions and input precedence are complete for an agent to choose correctly. The remaining gap is behavioral edge cases (no match, ambiguous name) and the two undocumented optional parameters, which matter given zero annotation coverage.

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 0% across four parameters, so the description must compensate. It does real work for two of them: product_id 'when known' and query as the exact product-name fallback, including the precedence rule that the tool resolves names internally. However, 'selected' and 'buyer_context' are never mentioned, leaving half the inputs with no meaning anywhere.

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?

Specific verb plus resource: 'Render the interactive detail UI for one exact Aari Clothing product.' It names what it is not (render_product_search, render_complete_the_look) and scopes to a single exact product, so an agent can separate it from the discovery and pair-recommendation siblings without opening the schema.

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?

Explicit positive triggers ('shopper explicitly asks to view, inspect, review, or get specifications for one exact product, or selects a product from search results') and explicit exclusions ('do not call it automatically to rank, compare, validate, or explain discovery results'). It also names the alternative for pair/matching intent and forbids a wasteful product-search round trip first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources