agentee

Check print generation

studio_status

Read-onlyIdempotent

Check a custom print generation. Args: print_id (from studio_generate). When done returns preview_url — show it to the human.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`print_id`	Yes	Generation id returned by studio_generate.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`error`	No	Generation failure reason (credits are refunded).
`detail`	No
`status`	No	Generation state; 'done' and 'failed' are terminal.
`print_id`	No
`design_url`	No	Shareable Studio design page (when done) — the link to SHARE with the human.
`preview_url`	No	Raw print image (when done) — embed/attach it so the human sees the print in chat.

TDQS

A4.7/5.0

Behavior5/5

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

Description adds context beyond annotations: specifies that when generation is done, it returns a preview_url. Aligns with readOnlyHint and idempotentHint.

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?

Extremely concise: one sentence plus a short argument note. No wasted words; front-loaded with purpose and key information.

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 simple single-parameter tool with output schema, the description fully covers usage: what to pass in, what to expect (preview_url), and what to do with it.

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 100% with a single parameter. Description adds value by indicating the parameter comes from studio_generate, aiding correct usage.

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 checks a custom print generation and returns a preview_url. It distinguishes from sibling tools like studio_generate by specifying the parameter source.

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?

Explicitly mentions the required print_id from studio_generate and instructs to show the preview_url to the human. Does not explicitly state when not to use, but the context is clear.

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

All agentee 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.

Tools are mostly distinct; slight overlap exists between cart_update and set_cart_quantity (both modify cart lines), and between remove_promo and cart_remove (different domains). Other groups (studio, designer) are well-separated.

Naming Consistency5/5

Consistent use of verb_noun pattern for most tools, with noun prefixes (designer_, studio_) grouping related tools. No mixed conventions or obscure abbreviations.

Tool Count3/5

31 tools is high for a single server, covering shopping, studio, and designer domains. Some tools like cart_update and set_cart_quantity seem redundant, pushing count beyond optimal.

Completeness4/5

Core workflows (search, cart, checkout, generation, designer submission) are covered. Minor gaps: no edit/delete for designs or orders, and no tool to manage saved addresses beyond viewing.

Resources

Need Help?