Skip to main content
Glama

Get the artwork requirements for a job

get_artwork_requirements
Read-onlyIdempotent

What a print-ready file must be for a product and configuration: finished size, bleed, safe zone, the PDF page size including bleed, pages or sides expected, the spot plate names a spot finish needs, the cut line rule, resolution, accepted file types and the size limit. The same rules the product page's guide card uses. File-setup facts must come from this tool, never from general knowledge: Printdash's bleed differs from the 3 mm many printers use (5 mm on most products). The size comes from the configuration, so build it with match_options first ("A5" is a size id); without one, or without a size, the answer is for the product page's default job (assumed_configuration) and lists size_options to ask the customer from. The answer includes Printdash's own diagram as an image: show that one.

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": {
      "product_id": "<product_id>"
    },
    "name": "get_artwork_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes
configurationNoThe job, as for price_job (match_options builds it); its size sets the page size. Without one, or without a size, the answer is for the product page's default job (assumed_configuration), with size_options to ask from.

Output Schema

NameRequiredDescriptionDefault
nextYes
sidesYes
colourYes
guidesYes
bookletYes
productYes
bleed_mmYes
diagramsYes
cut_styleYes
product_idYes
max_file_mbYes
spot_platesYes
studio_noteNo
cut_to_shapeYes
dieline_ruleYes
safe_zone_mmYes
size_optionsYes
pages_expectedYes
resolution_dpiYes
spot_plate_ruleYes
finished_size_mmYes
for_this_productYes
pdf_page_size_mmYes
for_configurationYes
accepted_file_typesYes
preferred_file_typeYes
assumed_configurationNo
configuration_missingNo
configuration_problemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / configuration / properties / stickerShape / description
      Added value: +"Where get_product has a sticker_shape field: an id from it. Stickers: square, circle or custom; labels: rectangle, circle or custom."
    • changedInput schema / properties / configuration / properties / stickerShape / enum
      Previous value: -[
      -  "square",
      -  "circle",
      -  "custom"
      -]New value: +[
      +  "square",
      +  "rectangle",
      +  "circle",
      +  "custom"
      +]
  2. Changed5 schema fields changed
    • changedInput schema / properties / configuration / description
      Previous value: -"The job, as option ids from get_product. Everything optional: the result says what is missing."New value: +"The job, as for price_job (match_options builds it); its size sets the page size. Without one, or without a size, the answer is for the product page's default job (assumed_configuration), with size_options to ask from."
    • addedOutput schema / properties / assumed_configuration
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "configuration": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "reason": {
      +      "type": "string"
      +    },
      +    "size_label": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "configuration",
      +    "size_label",
      +    "reason"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / diagrams
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "alt": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "enum": [
      +          "bleed",
      +          "dieline",
      +          "booklet-pages"
      +        ],
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "title",
      +      "url",
      +      "alt"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / size_options
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "detail": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "product_id",
      -  "product",
      -  "for_configuration",
      -  "finished_size_mm",
      -  "bleed_mm",
      -  "safe_zone_mm",
      -  "pdf_page_size_mm",
      -  "sides",
      -  "pages_expected",
      -  "booklet",
      -  "cut_to_shape",
      -  "cut_style",
      -  "dieline_rule",
      -  "spot_plates",
      -  "spot_plate_rule",
      -  "resolution_dpi",
      -  "colour",
      -  "accepted_file_types",
      -  "preferred_file_type",
      -  "max_file_mb",
      -  "guides",
      -  "for_this_product",
      -  "next"
      -]New value: +[
      +  "product_id",
      +  "product",
      +  "for_configuration",
      +  "finished_size_mm",
      +  "bleed_mm",
      +  "safe_zone_mm",
      +  "pdf_page_size_mm",
      +  "sides",
      +  "pages_expected",
      +  "booklet",
      +  "cut_to_shape",
      +  "cut_style",
      +  "dieline_rule",
      +  "spot_plates",
      +  "spot_plate_rule",
      +  "resolution_dpi",
      +  "colour",
      +  "accepted_file_types",
      +  "preferred_file_type",
      +  "max_file_mb",
      +  "guides",
      +  "for_this_product",
      +  "size_options",
      +  "diagrams",
      +  "next"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safe read-only, idempotent profile, yet the description adds genuinely non-obvious behavior: Printdash bleed is 5 mm rather than the industry 3 mm, missing configuration silently falls back to the product's default job (assumed_configuration) plus size_options, and the response carries Printdash's own diagram image that should be shown. These are the kind of facts an agent could not infer and would otherwise get wrong.

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?

Front-loaded with the returned facts, then the source-of-truth rule, then the bleed caveat, then the configuration/fallback rule, then the image instruction — a sensible order. Sentences are dense and slightly run-on, but nearly every clause carries actionable information.

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 two-parameter tool with a nested job object and an output schema, the description covers the prerequisite, the fallback, the domain-specific bleed trap, and how to handle the returned image. What is missing is any routing against the similarly named get_artwork_guide sibling, which is the main remaining ambiguity.

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 only 50%, but the description compensates by explaining that the configuration object is the same job shape price_job takes, that match_options constructs it, that its size drives the page size, and that sizeId values are preset size ids ('A5'). It does not touch the remaining fields, leaving some of the 50% gap to the schema alone.

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

Purpose4/5

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

The description opens with a concrete inventory of what the tool returns (finished size, bleed, safe zone, PDF page size with bleed, pages/sides, spot plate names, cut line rule, resolution, file types, size limit), so an agent knows the exact resource. It does not distinguish itself from the sibling get_artwork_guide, which by name could be confused with this, so it falls short of a 5.

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 gives a hard rule for use ('File-setup facts must come from this tool, never from general knowledge') and a prerequisite ('build it with match_options first', 'A5 is a size id'). It also states the fallback path when no configuration or size is given, but never says when to prefer get_artwork_guide or another sibling instead.

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