Skip to main content
Glama

get_product_access

The only product access tool. Supports FREE downloads, purchased products, PRO and team entitlements. Get authorized access using this MCP token's current personal, PRO or team rights. Returns action=download with a temporary downloadUrl, or action=open_launcher with launcherUrl and installationUrl. After a purchase or subscription activates, retry with the same token; a user's statement of payment is not authorization. Personal and team purchases are not interchangeable. If access is still denied after payment, check the bound identity and allow time for payment settlement; do not immediately ask the user to pay again. D5 Launcher is a local desktop application. installationUrl identifies the D5 Render official website; local installation and launch status cannot be detected by this service. Client Skills handle installation guidance and local retries. productUrl is a product page, not an installer. Launcher checks its own signed-in account. Never claim a successful launch from this response. Domestic responses omit productUrl. Official HDRI Launcher actions are unsupported. D5A and D5M are asset formats, not delivery actions. Follow Web CTA rules: PAID products require verified purchase before download; FREE/PRO products with an official asset ID use Launcher, otherwise use the authorized download path. These Web delivery and entitlement rules apply to every upload source and to models, materials, textures and HDRIs. ACTION_UNSUPPORTED means the delivery action is unavailable, not missing purchase rights; never recommend payment to resolve it. Use get_product_detail.accessFiles to choose a fileId; omit fileId for official Launcher assets. Only PURCHASE_REQUIRED or SUBSCRIPTION_REQUIRED errors indicate missing purchase or subscription rights. For DOWNLOAD_UNAVAILABLE or SERVICE_UNAVAILABLE, retry later without asking for payment. Download links expire after expiresInSeconds; request this tool again to revalidate rights and obtain a fresh link. If multiple files are available and fileId is omitted, select from FILE_SELECTION_REQUIRED.fileIds and retry. create_free_download_url has been removed; do not call or fall back to it. 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_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdNoOptional Web file ID
productCodeYesProduct code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are supplied, and the description carries the load well: error-code semantics (PURCHASE_REQUIRED vs DOWNLOAD_UNAVAILABLE vs ACTION_UNSUPPORTED), link expiry via expiresInSeconds, identity/team entitlement separation, and the explicit limitation that local launch state cannot be detected. Some of that value is offset by noise about Skills and reminders that is not about this tool's behavior.

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?

A single dense wall of sentences mixing entitlement rules, sales-recovery policy, launcher/installer distinctions, Skill compatibility guidance, and host reminder policy. Core invocation guidance is not front-loaded enough and unrelated passages (Skill install/update, host loading success claims) are buried mid-text.

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

Completeness3/5

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

Coverage of entitlement and error behavior is extensive, but there is no output schema and the description never enumerates the response fields beyond action/downloadUrl/launcherUrl, and important issues (why a Skill-compatibility topic appears in an access tool) are left ambiguous. Complete-ish in volume, incomplete in clean framing.

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 would be 3, but the description adds meaning beyond the schema: where fileId comes from, when to omit it, and how to recover from FILE_SELECTION_REQUIRED.fileIds. productCode semantics remain thin (only 'Product Code').

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 opening lines do establish a verb and resource (get authorized product access, returning action=download with a downloadUrl or action=open_launcher with launcherUrl), but the purpose is diluted by long detours about Skill installation, host loading, and CTA rules. The claim 'the only product access tool' is not reconciled with siblings like get_product_detail, which the description itself references.

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 rules: use get_product_detail.accessFiles to choose a fileId, omit fileId for official Launcher assets, PAID products require verified purchase, FREE/PRO with official asset ID use Launcher. It also states what NOT to do (don't tell users to pay for ACTION_UNSUPPORTED, don't fall back to create_free_download_url), which is unusually actionable.

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