InkFE Print

Record customer proof approval

approve_design_proof

Idempotent

Only call after showing both front/back previews, warnings and exact print options and receiving explicit customer artwork approval in the AI conversation. Report frontReviewed, backReviewed and artworkApproved as true only when that happened. Records agent-reported approval for immutable artwork and configuration, not independent human-click evidence or payment consent. Returns approvalId, evidence and expiry. Repeated approval of identical terms is idempotent. Changed artwork or print options requires fresh review and approval. A new quote with unchanged print configuration can reuse the artwork approval; the buyer separately confirms commercial terms.

Input Schema

TableJSON Schema

Name	Required	Description
`guestToken`	No	Private 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.
`quoteToken`	Yes
`designToken`	Yes
`backReviewed`	Yes
`frontReviewed`	Yes
`artworkApproved`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`designId`	Yes
`evidence`	Yes	The AI app reported the customer's approval.
`expiresAt`	Yes	ISO-8601 UTC timestamp.
`proofHash`	Yes	Lowercase hex SHA-256 digest.
`approvalId`	Yes	Pass to create_checkout.
`approvedAt`	Yes	ISO-8601 UTC timestamp.
`instructions`	Yes
`printedSides`	Yes
`configurationHash`	Yes	Lowercase hex SHA-256 digest.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "approvalId": {
+      "description": "Pass to create_checkout.",
+      "type": "string"
+    },
+    "approvedAt": {
+      "description": "ISO-8601 UTC timestamp.",
+      "type": "string"
+    },
+    "configurationHash": {
+      "description": "Lowercase hex SHA-256 digest.",
+      "type": "string"
+    },
+    "designId": {
+      "type": "string"
+    },
+    "evidence": {
+      "const": "agent_reported",
+      "description": "The AI app reported the customer's approval.",
+      "type": "string"
+    },
+    "expiresAt": {
+      "description": "ISO-8601 UTC timestamp.",
+      "type": "string"
+    },
+    "instructions": {
+      "type": "string"
+    },
+    "printedSides": {
+      "items": {
+        "enum": [
+          "front",
+          "back"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "proofHash": {
+      "description": "Lowercase hex SHA-256 digest.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "approvalId",
+    "proofHash",
+    "configurationHash",
+    "approvedAt",
+    "expiresAt",
+    "evidence",
+    "designId",
+    "printedSides",
+    "instructions"
+  ],
+  "type": "object"
+}

First observedSep 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it discloses that approval is agent-reported, immutable, idempotent for identical terms, and separate from payment consent. It explains what happens when terms change and what the return value contains, all without contradicting the annotations.

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 dense but every sentence earns its place, with the most critical invocation condition front-loaded. It avoids filler and packs prerequisites, constraints, return values, idempotency, and reuse rules into a compact set of sentences.

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 output schema, annotations, and sibling tools, the description covers the important operational context: prerequisites, approval semantics, idempotency, changed-term behavior, reuse rules, and return fields. The only minor gap is token semantics, but the names and sibling context make those reasonably inferable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 17%, so the description must compensate for unclear parameters. It does clarify the three boolean parameters and their exact reporting conditions, but it does not explain the meaning, origin, or relationship of designToken and quoteToken, which are core required parameters with no schema descriptions.

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 clearly states the tool records agent-reported customer approval of artwork, with a specific prerequisite flow and explicit constraints on when the boolean flags may be true. It differentiates itself from related concepts by noting it is not independent human-click evidence or payment consent, which helps an agent distinguish it from checkout or payment tools.

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?

The description gives explicit when-to-call guidance: only after showing front/back previews, warnings, and exact print options and receiving explicit customer approval. It also provides exclusion and reuse guidance, such as changed artwork requiring fresh approval and unchanged print configuration allowing reuse in a new quote.

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

All InkFE Print tools Inspect

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

Need Help?