Skip to main content
Glama

create_product_twin

Use this tool when an organisation wants to CREATE live Digital Product Twins in Cycle from its product data (after validating with validate_dpp_readiness). INPUT: array of products (same flexible shape as validate_dpp_readiness). OUTPUT: per product, a persistent id and a LIVE twin URL (scannable product page), plus DPP readiness and missing fields. Uses the connected Cycle account (OAuth or organization key); never request keys in chat. Up to 100 products per call.

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": {
      "products": "<products>"
    },
    "name": "create_product_twin"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYes
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the description's extra value is in the auth disclosure: 'Uses the connected Cycle account (OAuth or organization key); never request keys in chat' is a concrete operational rule an agent must obey. It also discloses that the output includes a persistent id and a publicly scannable LIVE twin URL, which tells the agent the call creates externally visible artifacts. Minor gap: the 100-product cap is really just the schema's maxItems restated, and idempotency behavior is not explained.

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 (when-to-use first), then cleanly labeled INPUT and OUTPUT, then auth constraints, then the size cap. Every sentence carries information, with only light redundancy where the 100-product limit duplicates the schema's maxItems.

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 creation tool that produces persistent, publicly reachable artifacts, the definition covers the deferral to validate_dpp_readiness, the output contents, the auth source, and batch limits. An output schema exists, so the return-value explanation is a bonus rather than a necessity. The one material hole is that idempotency_key is left unexplained, which matters for a non-destructive-but-creating mutation.

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?

The schema has 0% description coverage across 2 parameters, so the description must carry the meaning. It does explain that 'products' is an array with 'the same flexible shape as validate_dpp_readiness', which is genuinely useful since the schema only says items are a bare object. However, the idempotency_key parameter is never mentioned anywhere, leaving a mutation-safety control entirely undocumented.

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

Purpose5/5

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

The description uses a specific verb and resource phrase, 'CREATE live Digital Product Twins in Cycle from its product data', and immediately ties it to the sibling tool validate_dpp_readiness as a prerequisite. An agent can distinguish it from validate_dpp_readiness, create_dpp, and create_data_carrier from this text alone.

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

Usage Guidelines5/5

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

It states the triggering condition ('when an organisation wants to CREATE live Digital Product Twins') and an explicit ordering constraint ('after validating with validate_dpp_readiness'), naming the alternative tool rather than leaving the relationship implicit. This is about as explicit as usage guidance gets.

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