Skip to main content
Glama

Preview a 3x3 set from nine images

preview_set
Read-onlyIdempotent

Build a printable set from exactly nine public image URLs, in grid order (left to right, top to bottom). Returns thumbnail previews, the price, and a set_hash to pass to place_order. Images must be JPEG or PNG, up to 10 MB each, reachable over plain https with no redirect. Private or internal addresses are refused. Nothing is charged and no order is created.

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": {
      "images": "<images>"
    },
    "name": "preview_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
imagesYesExactly nine image URLs in grid order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / email
      Removed value: -{
      -  "description": "Contact email. Used only if an order needs clarifying.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "images",
      -  "email"
      -]New value: +[
      +  "images"
      +]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, and the description adds substantial context: exact image count, format and size limits, https/no-redirect requirements, refusal of private addresses, and returned preview/price/hash. This is unusually complete behavioral disclosure.

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?

The description is front-loaded with the core action and ordering rule, then efficiently covers inputs, return values, and constraints. Every sentence contributes useful information without repetition.

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?

Given the simple one-parameter schema, rich annotations, and absence of an output schema, the description supplies everything needed to call the tool correctly. It explains input constraints, return values, and the relationship to place_order.

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?

The schema already documents the single images parameter at 100% coverage, including exact count and grid order. The description adds meaningful constraints beyond the schema, such as JPEG/PNG, 10 MB size limit, plain https without redirects, and rejection of private/internal addresses.

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 states a specific action and resource: building a printable set from exactly nine image URLs in grid order. It clearly distinguishes the preview step from sibling ordering tools by noting it returns a set_hash for place_order and creates no order.

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 clearly positions the tool as a preview step whose set_hash is passed to place_order, and states that nothing is charged and no order is created. It does not explicitly address when to use get_pricing or check_order instead, leaving some sibling routing implicit.

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