Skip to main content
Glama

PassFast

by st.passfa
OverviewDiscussionsAdmin

uploadImage

Upload an image

Uploads an image for use in pass templates or per-pass strip overrides. Send as multipart form data with a purpose field and a file field containing the PNG image.

Upload behaviour by purpose:

  • strip — accumulates. Each upload creates a new image; the returned id can be passed as strip_image_id on POST /v1/passes or PATCH /v1/passes/{id} to give individual passes their own banner. Previous strip images are NOT deleted — manage them via DELETE /v1/images/{id} when no longer referenced.

  • All other purposes (icon, logo, thumbnail, background, footer, and all _2x/_3x variants) — replace-on-upload. Uploading a new image of the same purpose deletes the previous one from storage and DB. These are app-wide template assets, not per-pass.

Scope: images:manage

Maps to OpenAPI operationId uploadImage — POST /manage-images.

Same PassFast HTTP API, billing, and rate limits. Do not invent other paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
purposeYesThe intended use of the image. `strip` uploads accumulate (for per-pass `strip_image_id` overrides); all other purposes replace existing uploads of the same purpose for the app.
filenameNoOptional filename sent with the multipart upload.
x_app_idNoOverride X-App-Id for this call. Defaults to the MCP connection header.
file_base64YesBase64-encoded file bytes. Maps to the OpenAPI multipart `file` field — same uploadImage (or equivalent) endpoint, not a new API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior1/5

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

The description is highly transparent, disclosing deletion of previous images on replace, accumulation of strip uploads, manual cleanup, scope, and rate limits. However, annotations declare destructiveHint=false while the description explicitly says uploading non-strip purposes deletes the previous image from storage and DB; this is a direct contradiction, so per rubric the score is 1 and the flag is set.

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?

The description is front-loaded with the core operation, then uses clearly labeled bullets to explain per-purpose behavior. It is lengthy but every section (mechanics, accumulation/replacement semantics, scope, API mapping, rate limits) earns its place.

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 tool with no output schema, it covers the essential call context: multipart format, purpose-specific behavior, scope, OpenAPI mapping, and the returned id's downstream use. It does not enumerate error conditions or exact response shape, but the provided information is enough for correct invocation.

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% and already describes purpose and file_base64 well. The description adds value by explaining the multipart field mapping, PNG expectation, and the meaning of the returned id for strip_image_id, going beyond the schema baseline.

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 opens with a specific verb and resource: uploading an image for pass templates or per-pass strip overrides. It also clearly distinguishes the operation from sibling image tools (listImages, deleteImage, getImageUsage) by describing the output and usage.

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 gives concrete when-to-use guidance: multipart fields, what to do with strip IDs on pass create/update, and which purposes accumulate vs replace. It doesn't explicitly name alternative tools for image management, but the behavior by purpose is specific enough to prevent misuse.

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

All PassFast toolsInspect
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