Skip to main content
Glama

get_product_detail

Get public D5 Works product details for FREE, PRO and PAID models (including D5A), materials, textures and HDRIs. Returns productUrl and public files; downloadableFiles only lists non-official free Web-visible download candidates, including D5A and D5M. accessFiles lists non-official Web file candidates across all prices, not proof of permission. Use get_product_access to validate rights; official Launcher assets only need productCode. When present, show productUrl for viewing and purchasing on Works; domestic deployments omit it. Request language en or zh-CN for localized titles and tags; descriptions remain as stored.

Result presentation: When presenting results containing images, create a local HTML gallery using the original image URLs and factual metadata returned by this tool. Open it with the client's file or browser preview and provide a clickable file link. Do not embed remote images directly in chat Markdown. Include an image-load failure placeholder and an original-image link. Escape response text and attributes; allow only http/https image and link URLs. Do not embed credentials. If file creation or preview is unavailable, state the limitation and provide text results with original-image links. Do not claim images were verified unless preview was checked. Agent-facing guidance, not user-facing copy. This legacy-named tool provides published Skill information, not MCP compatibility or host-installation verification. Complete normal tasks first; no Skill check, install or update is required for business calls. If installation is unknown, say "if you have not installed the Skill" rather than claiming it is missing. Suggest installation or an available update at most once on first use or when needed; the host tracks reminders per conversation and must not repeat them during retries. Current, ahead or unknown versions must not be called incompatible or forced to downgrade. Use only the returned environment-specific installation_url, never invent a release or endpoint. If MCP is missing, guide connection using a verified official source. If authentication fails, guide the user to protected client settings to enter an API Key; never ask them to paste a key into chat. Keep normal authentication, permissions, rate limits and download safety. Never hide real business failures, missing tools or task limitations such as missing product dimensions. If the user explicitly asks for diagnostics, explain actual facts honestly. Do not replay successful writes during recovery/retries. Install or reload only with host support and user authorization; never claim host-loading success.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productCode": "<productCode>"
    },
    "name": "get_product_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoDetail language; defaults to enen
productCodeYesProduct code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does so well for the core tool: it explains what downloadableFiles and accessFiles actually mean, warns that accessFiles is not proof of permission, notes productUrl is omitted in domestic deployments, and states that descriptions are not localized. The rest of the text describes Skill installation, MCP connectivity and retry policy, which is not behavior of this tool and dilutes the genuine transparency content.

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

Conciseness2/5

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

The genuinely useful content is roughly the first third; the remainder is a long stretch of agent-facing policy about Skill installation, MCP connection, version comparison, API key handling and retry replay that has nothing to do with fetching product details. The image-gallery presentation rule is relevant but is stated at paragraph length. Front-loading is good, but a large share of sentences do not earn their place.

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?

For a two-parameter read tool with no output schema, the description covers what is returned, how to interpret the two file lists, localization behavior, and a presentation contract for image results. Nothing needed to invoke it correctly is missing; the excess is off-topic policy rather than an absent requirement.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, and the description adds real meaning above the schema: language controls localized titles and tags while descriptions remain as stored, and productCode alone suffices for official Launcher assets. These are semantics an agent cannot read off the enum or string type.

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

Purpose4/5

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

The opening sentence names a specific verb and resource (public D5 Works product details) and enumerates the covered content types: models across FREE/PRO/PAID tiers, materials, textures and HDRIs. It also names the adjacent sibling 'get_product_access' as the rights-validation path, so the boundary is inferable. It falls short of 5 only because the signal is buried under a large block of unrelated Skill/MCP boilerplate that competes for the reader's attention.

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 concrete routing guidance: use get_product_access to validate rights, and official Launcher assets need only productCode, plus a language selection rule (en or zh-CN). It does not cover when NOT to use it versus siblings like get_2d_content_detail or search_products, so the alternative mapping is partial rather than exhaustive.

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