Skip to main content
Glama

Generate Physical Product With AI

generate_physical_product_with_ai

Generate a physical product draft from cover media using the LPBE AI generation flow. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "coverMediaItems": "<coverMediaItems>"
    },
    "name": "generate_physical_product_with_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
coverMediaItemsYesCover images or videos for the product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / coverMediaItems / description
      Added value: +"Cover images or videos for the product."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world mutation. The description adds substantial procedural behavior beyond annotations: FREE businesses are blocked, check_business_tool_access must be called first, grace-period warnings and resubscribe links must be shown, and blocked access must halt the workflow.

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?

The description is front-loaded with the purpose and then moves into access prerequisites. It is generally efficient, though the access-control instructions are somewhat repetitive around checking permissions and not proceeding when blocked.

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 mutation-generation tool with annotations and fully described parameters, the description covers the critical access-gating workflow thoroughly. It does not clarify the resulting draft's lifecycle or how it relates to create_physical_product, which leaves a minor contextual gap given there is no output schema.

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 100%, so the schema already documents communityId and coverMediaItems thoroughly. The description mentions cover media and business permissions but does not add syntax, constraints, or meaning beyond what the input schema provides, making the baseline 3 appropriate.

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 description states a specific verb and resource: 'Generate a physical product draft from cover media using the LPBE AI generation flow.' It distinguishes the AI-generation path from manual creation implicitly through 'from cover media' and 'LPBE AI generation flow,' but does not explicitly name or contrast with sibling tools like create_physical_product or generate_physical_product_cover_media.

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?

It gives clear prerequisite guidance: check business permissions, call check_business_tool_access before collecting inputs, and do not proceed for FREE businesses or when access is blocked. It does not explain when to choose this tool over alternatives such as create_physical_product, so alternative-selection guidance is missing.

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