Skip to main content
Glama

Start an image license for an artwork

start_image_license

Places an order to license the image of one work by Ryan Seslow, for the person or business you act for, and 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; once paid, the download opens. The order is governed by the AREMES Image License (https://aremes-enterprises.com/work/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>",
      "work": "<work>",
      "term": "<term>",
      "agree": "<agree>"
    },
    "name": "start_image_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
termYes1m = one month ($25), 1y = one year ($150), own = own it forever ($450).
workYesThe work's slug, e.g. "crown".
agreeYesTrue only if the licensee read and agreed to the AREMES Image License.
emailYes
projectNoOptional: what the image will be used for.
businessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations it discloses the payment semantics: no charge until paid, and the download opens only after payment, which tells the agent this creates a real commitment. It does not mention that repeated calls produce multiple orders (consistent with idempotentHint=false), which is the one behavioral detail left implicit.

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

Conciseness5/5

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

Three tight sentences: the core action first, then the return values and charge timing, then the license terms and the agree gate. Nothing repeats the name/title and nothing is wasted.

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 tool with seven parameters, no output schema, and real financial side effects, the description supplies everything needed: what it returns (order number, total, checkout link), when money moves, where the license lives, and the consent flag that must be true.

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?

With 57% schema coverage, the description carries useful weight by explaining that name/email/business belong to the licensee and by restating the critical meaning of agree. It adds little about "work" or "term" beyond what the schema already documents with prices, so it does not fully compensate for the remaining coverage gap.

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 names a specific verb+resource ("Places an order to license the image of one work by Ryan Seslow") and scopes it to image licensing, which separates it cleanly from the sibling start_model_license and start_space_license tools. An agent can tell what it does without opening the schema.

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 states the actor context ("for the person or business you act for") and the gating condition ("accepted only when agree is true"), giving clear preconditions for calling. It stops short of explicitly naming an alternative or a when-not-to-use case, so it is a strong 4 rather than a 5.

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