Brandize

Buy logo variation

buy_logo_variation

Purchase one of the alternate designs from generate_logo_variations instead of the original logo. Priced the same as the PREMIUM tier. Mints a short checkout link; once paid, the chosen variation becomes the job's deliverable — poll get_logo_result with the same jobToken to retrieve it. This is a paid purchase; the hosted checkout page collects the user's acceptance of the Terms of Service and Privacy Policy, so no separate consent step is needed here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`jobToken`	Yes	The jobToken returned by generate_logo.
`variationId`	Yes	The variationId of the design to purchase, from generate_logo_variations.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes	Guidance for completing payment and retrieving the deliverable.
`currency`	Yes	ISO currency code.
`jobToken`	Yes	The job this purchase belongs to.
`priceUsd`	Yes	PREMIUM price in US dollars.
`checkoutUrl`	Yes	Short checkout link to pay; null only if Stripe returned no URL.
`variationId`	Yes	The variation being purchased.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "checkoutUrl": {
+      "description": "Short checkout link to pay; null only if Stripe returned no URL.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "currency": {
+      "description": "ISO currency code.",
+      "type": "string"
+    },
+    "jobToken": {
+      "description": "The job this purchase belongs to.",
+      "type": "string"
+    },
+    "note": {
+      "description": "Guidance for completing payment and retrieving the deliverable.",
+      "type": "string"
+    },
+    "priceUsd": {
+      "description": "PREMIUM price in US dollars.",
+      "type": "number"
+    },
+    "variationId": {
+      "description": "The variation being purchased.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "jobToken",
+    "variationId",
+    "checkoutUrl",
+    "priceUsd",
+    "currency",
+    "note"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 10, 2026

removedInput schema / properties / acceptedTerms

Removed value: -{
-  "description": "The purchase is gated on Terms & Privacy consent. Before calling, give the user the Terms of Service and Privacy Policy links and ask them to accept as a multiple-choice question — \"Accept Terms & Privacy\" / \"Decline\". Pass true ONLY after the user picks accept; if they decline, stop and do not purchase. The checkout page will also require them to accept.",
-  "type": "boolean"
-}

changedInput schema / required

Previous value: -[
-  "jobToken",
-  "variationId",
-  "acceptedTerms"
-]New value: +[
+  "jobToken",
+  "variationId"
+]

First observedSep 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that this is a paid purchase, creates a checkout link, requires payment before the deliverable changes, and offloads Terms of Service/Privacy consent to the hosted checkout page. It also tells the agent to poll get_logo_result with the same jobToken. This is rich, useful behavioral context that goes far beyond readOnlyHint/destructiveHint.

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 core purpose and then covers payment, checkout, consent, and result retrieval in a compact flow. It is reasonably concise, though 'This is a paid purchase' is slightly redundant after 'Purchase' and 'Priced the same as the PREMIUM tier.' Overall it is well-structured and efficient.

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

Completeness5/5

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

For a two-parameter purchase tool with an output schema, the description covers the essential prerequisites, the payment/checkout flow, the deliverable transition, consent handling, and how to retrieve the purchased result. Nothing critical needed to call the tool correctly is missing.

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 the baseline is 3. The description adds meaningful context by confirming that jobToken is the same token used later with get_logo_result and that variationId comes from generate_logo_variations. This lifecycle relationship is not present in the schema and helps the agent use the parameters correctly.

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 opens with a specific verb and object: 'Purchase one of the alternate designs from generate_logo_variations instead of the original logo.' This clearly distinguishes the tool from generate_logo_variations (which generates designs) and generate_logo (which produces the original), leaving no ambiguity about what it does.

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?

The description gives clear context: it is for buying an alternate variation, not the original logo, and it references the correct source tool, generate_logo_variations. It also explains the post-purchase flow with get_logo_result. However, it does not explicitly state when not to use it or name direct alternatives as exclusions, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Brandize tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.