Skip to main content
Glama

create_reference

Create an upload slot for a reference image. Returns an upload URL and a ref_ token: upload the image file with one shell command (curl -T ''), then pass the ref_ token to the reference-image parameter you are filling - every parameter that takes reference images names this tool in its description. This is the ONLY way to supply reference images, and those parameters accept ref_ tokens and nothing else. Image data never goes inside a tool call: a call is JSON, so an embedded image would have to be base64 text that you, the caller, must emit character by character - slow, error-prone, and enough to exhaust your context window. The upload moves the bytes out-of-band instead: a plain HTTP PUT of the raw file, so any HTTP client works; if your environment has no way to send one, install curl. And when the image you want is from one of your OWN recent Logospell generations, skip the upload entirely: pass sourceGeneration and sourceImage and the server copies it directly - the shortcut for extending an existing set in its own style. Accepts PNG, JPEG, or WebP, each at most 500KB, each side between 64px and 768px - resize before uploading if needed; larger reference images do not improve results. A reference is private to your API key and can be used in any number of later calls; it expires 7 days after its last use or re-upload (each use restarts the window), so uploading a few references once can serve a whole session of work. To update a reference, upload a new file to the same upload URL: its image is replaced and its ref_ token stays the same. Costs no credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceImageNoOptional, with sourceGeneration: the delivered image filename to use as the reference, exactly as the generation's result, its manifest, or get_generations (the subjects in promptJSON) lists it (e.g. "a_lotus_cradling_a_glowing_pearl.png"). An image larger than the reference limits is downscaled to fit automatically.
sourceGenerationNoOptional, with sourceImage: fill this reference from one of your own recent generations instead of uploading a file. Pass the generation id - the random segment of its download URL (.../download/<id>/images.zip), also returned by list_recent_generations. The image is copied server-side; nothing is uploaded.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesToken to pass to a tool's reference-image parameter.
expiresAtYesWhen the reference expires if left unused, RFC3339.
uploadURLYesURL to PUT or POST the image file to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / sourceImage / description
      Previous value: -"Optional, with sourceGeneration: the delivered image filename to use as the reference, exactly as listed by list_recent_generations or the generation's manifest (e.g. \"a_lotus_cradling_a_glowing_pearl.png\"). An image larger than the reference limits is downscaled to fit automatically."New value: +"Optional, with sourceGeneration: the delivered image filename to use as the reference, exactly as the generation's result, its manifest, or get_generations (the subjects in promptJSON) lists it (e.g. \"a_lotus_cradling_a_glowing_pearl.png\"). An image larger than the reference limits is downscaled to fit automatically."
    • addedOutput schema / properties / expiresAt / description
      Added value: +"When the reference expires if left unused, RFC3339."
    • addedOutput schema / properties / ref / description
      Added value: +"Token to pass to a tool's reference-image parameter."
    • addedOutput schema / properties / uploadURL / description
      Added value: +"URL to PUT or POST the image file to."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the safety profile (not read-only, not idempotent, not destructive, closed-world), and the description adds far more: out-of-band upload mechanics, accepted formats (PNG/JPEG/WebP), size/dimension limits (500KB, 64-768px), API-key privacy, the 7-day sliding expiry, the same-URL replacement behavior, and zero credit cost. This is unusually rich behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core contract (create slot, upload, pass token) is front-loaded, and sentences are information-dense. It is somewhat verbose, with persuasive asides about curl and context-window exhaustion that justify rather than instruct, slightly diluting conciseness.

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?

Despite a separate output schema, the description still explains the meaningful return (upload URL and ref_ token) and covers limits, expiry, privacy, update semantics, and cost. Nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, so both sourceImage and sourceGeneration are already fully documented in the schema, and the description adds little beyond echoing that they enable a server-side copy. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opening sentence states a precise verb and resource ("Create an upload slot for a reference image") and immediately names the artifacts returned (upload URL and ref_ token). It is unmistakably distinct from siblings like delete_references, list_references, and the generation tools.

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?

It explicitly states this is the ONLY way to supply reference images, describes the two-step workflow (upload then pass ref_ token), and names the alternative path (sourceGeneration/sourceImage to skip the upload). When-to-use, when-not, and the alternative are all covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources