Skip to main content
Glama

Lorenzo — Premium Streetwear & Denim Shopping

Product details

product_details

App-only normalized data lookup for one Lorenzo product.

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": "product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
selectedNo
product_idNo
track_actionNo
buyer_contextNo
source_surfaceNoproduct_detail

Output Schema

NameRequiredDescriptionDefault
typeNoproduct_detail_result
storeYes
messageYes
productYes
selectedNo
sizeGuideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/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 and largely abdicates it. It never mentions the side effect implied by track_action defaulting to true (an action is recorded), nor whether the lookup is read-only, cached, or scoped to a buyer_context.

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?

A single front-loaded sentence with no bloat, so it is structurally clean. It is under-specified rather than verbose, which is a lesser but real defect for a six-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six optional parameters, no annotations, and nested array/object inputs, the description is far too thin to guide correct invocation. The presence of an output schema relieves it of explaining return values, but the input-side gaps remain severe.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, and the description compensates for none of them. 'For one Lorenzo product' faintly implies product_id, but query, selected, track_action, buyer_context, and source_surface are entirely undescribed anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a read-style verb ('lookup') and a resource ('normalized data ... for one Lorenzo product'), so the general intent is inferable. However, 'Lorenzo' and 'app-only normalized data' are unexplained jargon, and it gives no signal distinguishing it from siblings like render_product_detail or complete_look_product_details.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus render_product_detail (rendering) or complete_look_product_details. 'App-only' hints at a caller restriction but is ambiguous about whether that means a UI app context versus an API client.

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