Skip to main content
Glama

Get a Printdash artwork guide

get_artwork_guide
Read-onlyIdempotent

Printdash's artwork setup guides as Markdown (bleed and safe zone, print-ready PDFs, colour, double-sided, cut lines, spot finishes, lamination, stocks, white ink, booklets, folding, wide format, Illustrator and InDesign export). Without a topic, the list. With a product (and its configuration), what that product's page says on the topic, sized for the job. The bleed, cut-line and booklet topics include Printdash's own diagram as an image: show that one, not a diagram from elsewhere. Answer file-setup questions from these tools, never from general knowledge: Printdash's bleed differs from the 3 mm many printers use.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_artwork_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoA guide id (bleed, pdf-export, colour, double-sided, dieline, spot-finishes, lamination, stock-finishes, white-ink, booklets, folding, wide-format, export-illustrator, export-indesign). Omit for the list.
product_idNoA product, for what its page says on the topic.
configurationNoThe job, to size the product's lead (page size with bleed, pages, plate names).

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
nextYes
guideNo
titleNo
guidesNo
productNo
summaryNo
diagramsNo
product_idNo
studio_noteNo
for_this_productNo
on_this_products_cardNo
hidden_for_this_productNo

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. Changed1 schema field changed
    • 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"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behaviour, and the description adds real value on top: output is Markdown, some topics embed Printdash's own diagram image, and the agent must show that diagram rather than one from elsewhere. It doesn't describe pagination or size of the returned guides, which output schema may cover.

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 purpose, then mode rules, then behavioural caveats about diagrams and general knowledge. The parenthetical topic catalogue duplicates the schema's enum list and costs some space, but the prose itself is dense and each sentence carries instruction.

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?

For a three-parameter tool with a deeply nested configuration object, the description covers modes, output format and diagram handling, and output schema covers return shape. However, it never tells the agent how the configuration object affects which guide variant is returned beyond 'sized for the job', leaving the most complex parameter under-explained at the description level.

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 100%, so the parameters are already documented, including the topic id list and nested configuration fields. The description adds the interaction between topic, product_id and configuration ('sized for the job') and what omitting topic does, but largely restates the schema's own note about omitting topic. Baseline 3 fits.

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 names a concrete resource ('Printdash's artwork setup guides as Markdown') and enumerates the covered topics, so an agent knows exactly what comes back. It also spells out the two invocation modes (list vs. product/topic-specific). It does not distinguish itself from the close sibling get_artwork_requirements, so it stops 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?

Clear contextual routing: 'Without a topic, the list' and 'With a product (and its configuration), what that product's page says on the topic'. It also gives an explicit when-not: never from general knowledge, since Printdash's bleed differs from the common 3 mm. No sibling alternative is named, so not 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