Skip to main content
Glama

Start a 3D model license

start_model_license

Places an order to license one AREMES 3D model (the GT, the Sport Bike, the V-Twin Cruiser, the three Interdimensional Suits, the Parts in the Round, two relief sculptures and the twelve AREMES Furniture pieces) as GLB and USDZ files, for the person or business you act for. Returns the order number, the total and a Stripe checkout link for the licensee to pay by card; nothing is charged until it is paid. The order is governed by the AREMES 3D Model License (https://aremes-enterprises.com/vehicles/license/) and is accepted only when agree is true, meaning the licensee has agreed to it.

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": {
      "name": "<name>",
      "email": "<email>",
      "model": "<model>",
      "term": "<term>",
      "agree": "<agree>"
    },
    "name": "start_model_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
termYes1m = one month ($25), 1y = one year ($150), own = perpetual ($450). A furniture piece (sofa, chair, table, lamp, planter, bench, desk, deskchair, diningtable, diningchair, bed, nightstand) has two terms only: 1y = one-year license ($50), own = perpetual license ($150). Every term is a non-exclusive license, never a sale of the design.
agreeYesTrue only if the licensee read and agreed to the AREMES 3D Model License.
emailYes
modelYes
projectNo
businessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / model / enum
      Previous value: -[
      -  "gt",
      -  "bike",
      -  "cruiser",
      -  "suit",
      -  "suit-helmet",
      -  "suit-headset",
      -  "crown",
      -  "shoulder",
      -  "yoke",
      -  "hip-block",
      -  "shin",
      -  "pod",
      -  "helmet-4",
      -  "chest",
      -  "wood-wall",
      -  "cardboard"
      -]New value: +[
      +  "gt",
      +  "bike",
      +  "cruiser",
      +  "suit",
      +  "suit-helmet",
      +  "suit-headset",
      +  "crown",
      +  "shoulder",
      +  "yoke",
      +  "hip-block",
      +  "shin",
      +  "pod",
      +  "helmet-4",
      +  "chest",
      +  "wood-wall",
      +  "cardboard",
      +  "sofa",
      +  "chair",
      +  "table",
      +  "lamp",
      +  "planter",
      +  "bench",
      +  "desk",
      +  "deskchair",
      +  "diningtable",
      +  "diningchair",
      +  "bed",
      +  "nightstand"
      +]
    • changedInput schema / properties / term / description
      Previous value: -"1m = one month ($25), 1y = one year ($150), own = perpetual ($450)."New value: +"1m = one month ($25), 1y = one year ($150), own = perpetual ($450). A furniture piece (sofa, chair, table, lamp, planter, bench, desk, deskchair, diningtable, diningchair, bed, nightstand) has two terms only: 1y = one-year license ($50), own = perpetual license ($150). Every term is a non-exclusive license, never a sale of the design."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false; the description adds genuinely new behavior: a Stripe checkout link is returned, nothing is charged until payment, and the license is non-exclusive and only accepted when agree is true. It omits auth requirements and what happens on repeat calls given idempotentHint=false.

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

Conciseness3/5

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

The core behavior (order, price, checkout link, agree gate) is front-loaded, but the long parenthetical catalogue of models is verbose and ambiguous rather than informative, and the single dense sentence bundles pricing terms with legal terms.

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?

Return values are well covered despite no output schema (order number, total, Stripe link), which is a real strength. Still, for a 7-parameter write-order tool it leaves 'project', the enum naming, and any authentication/payment-precondition context unexplained.

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 coverage is only 29%, and the description partly compensates by explaining agree (must be true) and that the license is for the person or business being represented (name/email/business). However it never explains 'project', and its prose model list ('three Interdimensional Suits', 'Parts in the Round') does not map cleanly onto enum values like suit-helmet, yoke, hip-block, wood-wall, or cardboard, leaving several params under-explained.

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?

States a concrete verb and resource ('Places an order to license one AREMES 3D model') and names the deliverable formats (GLB and USDZ), which distinguishes it from the image- and space-license siblings by resource type.

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

Usage Guidelines3/5

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

Implies when to use it (licensing a 3D model on behalf of a person or business), but never states when to prefer start_image_license or start_space_license, nor any prerequisites such as needing an account or API credential.

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