Skip to main content
Glama

Dream Is Free — Streetwear, Denim & Hoodies

Product details

product_details

App-only normalized data lookup for one Dream Is Free 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.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing beyond implying a read via "lookup". Critically, it never mentions that the track_action parameter defaults to true, meaning a nominal "lookup" may record an analytics event — an undisclosed side effect. Permissions, cost, and failure behavior are all unstated.

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?

It is a single front-loaded sentence with no filler, so structure is fine. The brevity is under-specification rather than genuine conciseness, since the one sentence omits information an agent needs.

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?

An output schema exists, so return values need not be explained. But for a six-parameter tool with zero annotation coverage and zero schema descriptions, a single sentence leaves the agent without the parameter meaning, side-effect disclosure, or sibling routing needed to invoke it correctly.

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

Parameters1/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 explains none of them: query, selected, product_id, track_action, buyer_context, and the source_surface enum are entirely undocumented in prose. The phrase "one ... product" only faintly gestures at product_id and gives no meaning for the rest.

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?

The sentence names a resource (one Dream Is Free product) and a vague operation ("normalized data lookup"), so the intent is inferable but the verb is not a concrete action like get/fetch. "App-only" is unexplained jargon, and nothing separates this from siblings such as complete_look_product_details or render_product_detail.

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 when-to-use guidance, no prerequisites, and no named alternative. The only contextual hint is the opaque "App-only" qualifier, which an agent cannot act on when choosing between this and the several product-related siblings.

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