Skip to main content
Glama

InkFE Print

by com.inkfe
OverviewDiscussionsAdmin

Create a business card design

create_business_card_design
Idempotent

Applies the buyer's field values (and logo, if the template needs one) to a template, fits the text to its printable area, renders both sides as preview images, and returns a design token. Before creating a guest design, explain: unpaid, unsaved drafts expire 30 days after the design request starts. Verified saving keeps the draft; checkout and unresolved purchase artwork is protected. Seven-day token expiry is separate from deletion. Call list_business_card_templates first and collect a non-blank value for every field it lists, keyed by attribute; a blank or missing value fails with missing_required_fields. Pass a public https PNG or JPEG URL as logoUrl only when the template has an imageUrl field; omit it otherwise. Returns designToken, designId, templateId, revisionId, expiresAt (7 days out), previews (a 300-second signed URL plus width/height for each side; the pixels are also attached as image content blocks), and any text_shrunk warnings from fitting a value to its layer. Present both attached proof images directly, or provide labeled front/back links to the exact preview URLs if the host cannot display them. Do not require computer setup, downloads or re-uploading for proof review. Refresh expired links rather than creating another design. An accountOwned result identifies a verified customer, not an integration key. Results also include a private saveUrl for browser ownership verification; offer it only when the buyer wants to save. Saving requires sign-in; subsequent checkout of that design requires an AI connection authorized by the same InkFE account. If customer OAuth is unavailable, complete checkout before saving. Use a stable requestId; retry the same request after a timeout. Revise with revise_business_card_design and refresh expired links with refresh_design_proof. Show both previews and warnings, get exact print options and get_quote, then record explicit customer approval with approve_design_proof before create_checkout. Fails with unknown_template, missing_required_fields {attributes}, unknown_field {attribute}, value_too_long {attribute}, unsupported_characters {attribute}, logo_required, logo_fetch_failed, logo_unsupported, rate_limited {retryAfterSeconds} (too many designs from this API key in a short time), or connector_unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesEvery attribute from the chosen template's `fields` list (see list_business_card_templates) is required, keyed by `attribute`, with the buyer's text for it. Do not include the logo field here: pass its image via logoUrl instead. A blank or missing value fails with missing_required_fields.
logoUrlNoA public https URL to a PNG or JPEG logo image, required only when the template has an imageUrl field (see list_business_card_templates). Omit it for every other template.
requestIdYesA new stable requestId for each intentional design/revision. Reuse the same id and inputs after a timeout; never automatically replace an in-progress request.
guestTokenNoPrivate guestToken from start_guest_session, required only for anonymous guest design and checkout. Omit when connected through InkFE customer sign-in (OAuth) or a provisioned integration key; those connections must not start a guest session. Keep guest tokens in this conversation; never put them in a URL or share them.
templateIdYesThe templateId from list_business_card_templates identifying which Classic business card to design.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only indicate idempotent, non-read-only, non-destructive behavior, but the description adds substantial context: guest-draft expiry, seven-day token expiry, saveUrl ownership, sign-in/OAuth requirements, retry semantics for a stable requestId, and failure modes. It aligns with and enriches the idempotentHint rather than contradicting it.

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?

The description is dense and front-loaded with the core behavior, and nearly every sentence carries important operational detail. However, it is a very long single paragraph with many embedded user-facing instructions and workflow rules, which makes it harder to scan; bulleted or sectioned formatting would improve structure without losing content.

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?

With no output schema, the description fully compensates by enumerating return values (designToken, designId, previews, expiresAt, warnings), explaining preview URL behavior, listing error codes, and covering authorization, expiry, and downstream workflow steps. An agent has enough context to invoke the tool correctly and handle its results.

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 covers all five parameters at 100% coverage, so the baseline is 3. The description adds meaningful extra semantics: fields must be non-blank and keyed by attribute, logoUrl is omitted unless the template has imageUrl, and blank/missing values fail with missing_required_fields. It does not add much about guestToken, but the schema already documents that fully.

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 opens with a specific verb and resource: applying field values and a logo to a template, fitting text, rendering previews, and returning a design token. It clearly distinguishes itself from siblings by naming revise_business_card_design and refresh_design_proof as the alternatives for revisions and expired links.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs the agent to call list_business_card_templates first, to use revise_business_card_design for revisions, and to refresh expired links instead of creating another design. It also ties this tool into the larger checkout flow by naming approve_design_proof and create_checkout as follow-up steps, making when-to-use unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InkFE Print toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources