InkFE Print

Start an InkFE guest session

start_guest_session

Only for anonymous callers when guest access is enabled. If this AI app is already connected through InkFE customer sign-in (OAuth) or a provisioned integration key, skip this tool and omit guestToken on design/checkout calls. Before guest designing, tell the customer: unpaid, unsaved guest drafts expire 30 days after the design request starts; save through verified sign-in to keep them. Checkout or unresolved purchase records are protected. Returns a private guestToken valid for seven days; token expiry is separate from draft retention. Pass it to create_business_card_design and create_checkout in this conversation. Claimed designs require an AI connection authorized by the same InkFE account. Starting a session does not place or pay for an order.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`expiresAt`	Yes	ISO-8601 UTC timestamp.
`guestToken`	Yes	Private guest capability; pass on design and checkout calls.
`instructions`	Yes
`draftRetention`	Yes

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": {
+    "draftRetention": {
+      "type": "string"
+    },
+    "expiresAt": {
+      "description": "ISO-8601 UTC timestamp.",
+      "type": "string"
+    },
+    "guestToken": {
+      "description": "Private guest capability; pass on design and checkout calls.",
+      "type": "string"
+    },
+    "instructions": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "guestToken",
+    "expiresAt",
+    "draftRetention",
+    "instructions"
+  ],
+  "type": "object"
+}

First observedSep 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations are present but minimal (all false). The description adds substantial behavioral context: token validity (seven days), separation of token expiry from draft retention, that starting a session does not place/pay for an order, and that claimed designs require an authorized AI connection. It also mentions protected checkout records. This far exceeds the annotation coverage.

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 structured logically: condition first, then exclusions, then customer disclosure, then token details and usage, then claims and order implications. Every sentence carries critical information with no filler. It is front-loaded and efficiently organized.

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?

For a session-starting tool with side effects and constraints, the description covers all essentials: eligibility, exclusions, customer messaging, token validity, usage directions, claim requirements, and order implications. There is an output schema present, so return format is not needed. Nothing an agent needs to correctly invoke and use this tool is missing.

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 tool has zero parameters, so the schema fully covers parameters. The description adds no parameter-specific details (none needed), but it explains the return token and its usage, which is relevant context. Baseline 4 is appropriate for a no-parameter tool.

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 states a specific verb and resource: start a guest session. It explicitly scopes to anonymous callers when guest access is enabled, and differentiates from siblings by stating when to skip (if already connected via OAuth or integration key). This clearly distinguishes it from other tools like revoke_guest_session or create_checkout.

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?

Provides explicit when-to-use (anonymous callers when guest access is enabled) and when-not-to-use (if already connected, skip and omit guestToken). It also directs the token to specific sibling tools (create_business_card_design, create_checkout) and includes customer communication requirements. This is comprehensive usage guidance.

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?