AirGallery

save_artwork

Save an artwork to the authenticated user's gallery. A data:image URI (PNG, JPEG, WebP or GIF) is uploaded to AirGallery storage and the artwork stores the resulting public URL; http(s) URLs are stored as given. Requires auth + 'write' scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_url": "<image_url>"
    },
    "name": "save_artwork"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Tags for the artwork
`model`	No	AI model used
`preset`	No	Preset/style used
`prompt`	No	Prompt used to generate the image
`image_url`	Yes	http(s) image URL, or a data:image/…;base64 URI up to ~10 MB (e.g. a create_image result)
`is_public`	No	Whether to make the artwork public (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations at all, the description carries the burden well: it discloses a real side effect (uploading data to AirGallery storage and rewriting the input into a stored public URL), the auth requirement and required 'write' scope, and the differing treatment of http(s) versus data URIs. It does not address duplicate handling, idempotency, or rate limits, so it is strong but not exhaustive.

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, front-loaded with the action, then the input-handling rule, then the auth prerequisite. Every clause adds a distinct fact; nothing is padded or restated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter write tool with full schema coverage but no output schema, the description covers side effects, prerequisites, and input transformation. It omits what the call returns (e.g. the created artwork record or its id) and how a saved artwork relates to a preceding create_image call, which are the remaining gaps.

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%, so the baseline is 3; the description earns a bump by enumerating the supported image formats (PNG, JPEG, WebP, GIF) and explaining that a data URI is re-hosted while an http(s) URL is passed through, which is actionable constraint information not fully spelled out in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb and resource ("Save an artwork to the authenticated user's gallery") and states the scoping to the caller's own gallery. It never names or contrasts a sibling, so an agent must infer when to persist via save_artwork versus generating via create_image, which keeps it below 5.

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?

Gives clear operating context: two accepted input forms and what happens to each, plus the auth/scope prerequisite. It stops short of stating exclusions or naming alternatives, so there is no explicit when-not guidance.

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

All AirGallery 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?