agentee

Get an upload URL

designer_upload_slot

Get a short-lived URL to upload an image file to us (use when the designer has no public link — otherwise pass the URL straight to submit_design). Args: filename?. PUT the raw bytes to upload_url, then pass the returned upload_id to submit_design.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filename`	No	Original file name, for readability.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`pitch`	No	Designer-program pitch to relay to the user — present when is_partner is false.
`method`	No
`upload_id`	No
`expires_in`	No	Seconds the URL stays valid.
`is_partner`	No
`upload_url`	No
`how_to_join`	No	How to join the designer program — present when is_partner is false.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=false. Description adds behavioral steps (PUT bytes, pass upload_id) and notes the URL is short-lived, which is useful context beyond 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?

Extremely concise: two sentences that front-load the main purpose and include crucial usage instructions. No redundant words.

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 output schema existing, description doesn't need to detail returns. It sufficiently explains the two-step workflow (get URL, upload, pass ID) for a simple upload tool.

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?

Only one optional parameter 'filename' with schema description already providing meaning. Tool description mentions filename? but adds no extra value beyond schema. Schema coverage is 100%, baseline 3.

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 gets a short-lived upload URL for image files, and distinguishes from sibling tool 'submit_design' by specifying when to use each.

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?

Explicitly states when to use: 'use when the designer has no public link — otherwise pass the URL straight to submit_design'. Provides clear context and alternative.

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.

TDQS

A3.9/5.0

Disambiguation4/5

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?