Tintin Tryon

Get preview status

get_preview_status

Read-only

Poll a free preview. When succeeded, returns the preview image URL (valid 1h). No account needed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`preview_id`	Yes	Preview UUID returned by create_preview_job

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Machine-readable error code (only present on failures)
`job_id`	No	Generation job UUID
`status`	No	Job state: queued \| running \| succeeded \| failed
`message`	No	Human-readable explanation of the failure
`output_urls`	No	Presigned result image URLs (present when succeeded)
`error_message`	No	Failure detail when status is failed
`output_urls_expire_in`	No	Seconds until output_urls expire (3600)

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, it discloses that no account is needed and that the returned URL is valid for 1 hour. This adds practical context about rate limits/lifetime without contradicting 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?

Three short sentences, each providing unique value: purpose, success result, and access requirement. No redundancy, perfectly front-loaded.

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 simple poll tool with one parameter and an output schema, the description is complete. It mentions the success response, URL validity, and no-account requirement, covering all necessary usage context.

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% with a detailed description for preview_id ('Preview UUID returned by create_preview_job'). The description adds no additional parameter semantics beyond what the schema already covers.

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 polls a preview and returns the preview image URL on success. The verb 'Poll' and resource 'preview' make it distinct from sibling tools like get_job_status, which is more generic.

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?

It provides clear context for when to use: polling a preview until success. It does not explicitly exclude get_job_status or mention alternatives, but the 'free preview' scope makes the intended use obvious.

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

All Tintin Tryon tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct function: auditing a store, creating preview/tryon jobs, polling their statuses, checking credits, and getting seasonal guides. The preview vs tryon separation is clear, and audit_store explicitly references create_tryon_job, avoiding confusion.

Naming Consistency5/5

All tool names follow a strict verb_noun pattern (audit_store, create_preview_job, create_tryon_job, get_credits_balance, get_job_status, get_preview_status, get_seasonal_guide). Verb choices are consistent and the pattern is immediately predictable.

Tool Count5/5

Seven tools is well-scoped for this domain. Each tool serves a distinct part of the workflow—audit, preview, tryon generation, status polling, credit management, and seasonal guidance—with no redundancy or unnecessary extras.

Completeness5/5

The tool set covers the full lifecycle for both preview and tryon workflows: audit to identify needs, create jobs, poll status, and manage credits. The seasonal guide provides context for the audit. There are no obvious dead ends or missing operations for the stated purpose.

Resources

Need Help?