NIMGEN
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NVIDIA_API_KEY | Yes | Your NVIDIA API key (starts with nvapi-...) | |
| NIMGEN_BASE_URL | No | Custom NIM endpoint for self-hosted NIM | https://ai.api.nvidia.com/v1/genai |
| NIMGEN_OUTPUT_DIR | No | Directory to save generated images | ./nimgen-output |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate an image from a text prompt using NVIDIA NIM FLUX models. Returns the file path of the saved image. Use 'flux-1-dev' for high quality or 'flux-1-schnell' for speed. |
| edit_imageA | Edit an existing image using text instructions via FLUX.1-Kontext. Provide a source image path and describe the desired changes. Great for mockups, style transfer, and contextual editing. |
| list_modelsA | List all available FLUX models on NVIDIA NIM and their capabilities. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: generate_image creates new images, edit_image modifies existing ones, and list_models provides model information. No functional overlap exists, so an agent can select the correct tool without ambiguity.
All tool names follow the same verb_noun pattern with clear, action-oriented verbs (generate, list, edit) and consistent snake_case formatting. The pattern is predictable and easy to extend.
Three tools is well within the typical 3-15 range and perfectly scoped for an image generation/editing server. Each tool serves a necessary role with no bloat or redundancy.
The toolset covers the core workflow: generating new images, editing existing ones, and discovering available models. There are no obvious dead ends or missing operations critical to the domain.