Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SNAPGEN_API_KEYYesYour snapgen API key (create one at https://snapgen.ai/profile/integration/api-keys)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
generate_imageB

Generate an image with snapgen nano-banana models. POST /uapi/v1/generate_image. Returns a job; poll with get_generation.

generate_gpt_imageC

Generate an image with GPT Image 2. POST /uapi/v1/imagen/gpt-image-2. Premium plan required by snapgen.

generate_grok_imageC

Generate an image with Grok. POST /uapi/v1/imagen/grok.

generate_videoC

Submit a video job. family selects the documented path. Returns a uuid to poll with get_generation.

get_generationB

Fetch one generation by uuid. GET /uapi/v1/history/{uuid}. status 1 processing, 2 completed, 3 failed.

list_generationsC

List recent generations. GET /uapi/v1/histories.

wait_for_generationB

Poll a generation until it completes, fails, or the timeout is hit. Does not resubmit the job.

snapgen_requestC

Call any snapgen path under /uapi. Use when a model ships before this server is updated. path must start with /uapi/.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 8 tools

Disambiguation4/5

The three image generators are distinguished by model (nano-banana vs GPT vs Grok), though the generic name 'generate_image' for nano-banana is slightly misleading next to 'generate_gpt_image'/'generate_grok_image'. get_generation vs wait_for_generation are separable (fetch once vs poll to completion), and snapgen_request is a documented escape hatch, but it technically overlaps with every other tool.

Naming Consistency4/5

Strong verb_noun pattern throughout (generate_*, get_generation, list_generations, wait_for_generation). The only deviation is snapgen_request, which breaks the verb_noun convention but is still readable and clearly scoped as a fallback.

Tool Count5/5

Eight tools is well within the sweet spot, with generation, polling, retrieval, listing, and a documented catch-all each earning a distinct slot. No redundancy that would justify trimming.

Completeness4/5

Full lifecycle is covered: submit (generate_image/video), poll (wait_for_generation), fetch (get_generation), and list (list_generations). No delete/cancel operation exists, but snapgen_request provides an escape hatch for uncovered endpoints like cancellation.

Maintenance

ActivityMaintained
ResponsivenessNo issues