Skip to main content
Glama

Get a dieline

get_dieline

Draw a print-ready dieline at an exact size in the signed-in person's Drint space and return a download link (valid one hour): PDF / AI (cut and crease as spot colours with dimensions, opens in Illustrator) or SVG (CUT / CREASE layers). Give a standard code (FEFCO "0201", "0427"; ECMA "A20.20.03.01", "A60.20.00.01") or a Drint type id from list_dielines. Length, width, height are the inside size in mm. Dieline downloads (PDF / AI, SVG and the die-maker's DXF or CF2) need Pro; Free designs on the die in Drint. Pro has unlimited dieline downloads.

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_dieline"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoA FEFCO or ECMA code, e.g. "0201", "FEFCO 0427", "A20.20.03.01". Give this or type.
langNoThe user's language (vi, en, th, zh…). Default en.
nameNoA short file name, e.g. the product. Optional.
typeNoA Drint type id from list_dielines, e.g. "rte", "bag", "pillow". Give this or code.
formatNoFree default: SVG. Pro default: PDF / AI.
width_mmNo
height_mmNo
length_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"Default pdf."New value: +"Free default: SVG. Pro default: PDF / AI."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations mark this as a non-read-only, non-idempotent, non-destructive write with no open-world access; the description corroborates that by saying the dieline is drawn in 'the signed-in person's Drint space'. Beyond the annotations it adds genuinely useful behavior: the download link expires after one hour and downloads require a Pro plan, with Pro getting unlimited dieline downloads.

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-loads the action and the return value in the first sentence, then packages formats, identifier options, units and plan limits compactly. Dense but nearly every clause carries information; only the parenthetical format details edge toward overload.

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 an 8-param creation tool with no output schema, the description covers what is returned (a time-limited download link), the output variants, size units and entitlement gating. It leaves open what happens when both code and type are omitted (all params are optional) and whether an existing design is created or discarded on failure.

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 63%, and the description compensates by defining the geometry semantics ('Length, width, height are the inside size in mm'), which the schema's bare min/max bounds do not convey. It also clarifies the code-vs-type and format defaults, though individual params like lang and name get no treatment beyond the schema.

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 specific verb and resource: 'Draw a print-ready dieline at an exact size' and 'return a download link'. It also enumerates the concrete output artifacts (PDF/AI with spot colours and dimensions, SVG with CUT/CREASE layers), so an agent knows exactly what the call produces.

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?

Gives explicit routing for the identifier inputs ('Give a standard code ... or a Drint type id from list_dielines'), which points the agent at a sibling for valid ids. It also states access conditions (Pro needed for dieline downloads in PDF/AI/SVG/DXF/CF2, Free cannot download) with no explicit when-not-to-use or comparison against make_dieline.

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.