upres
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPRES_API_KEY | Yes | Your upres.ai API key. Generate one at https://upres.ai/account/api-keys (shown only once). |
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 |
|---|---|
| upres_list_modelsA | List UpRes upscale models (flare, prism, lumen, mirage, motion, motion-x) with use cases. |
| upres_get_creditsA | Show recent job count for the authenticated UpRes API key as a quota proxy. |
| upres_upscale_imageB | Submit an image upscale job from a public URL. Models: flare, prism, lumen, mirage. |
| upres_upscale_videoA | Submit a video upscale job from a public URL. Models: motion, motion-x. |
| upres_get_jobA | Get status and result_url of an UpRes job by id. |
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 5 tools
Each tool maps to a unique action or resource: model discovery, quota check, image upscaling, video upscaling, and job retrieval. The two upscale tools are clearly separated by media type and supported models, so there is no real ambiguity.
All tool names share the upres_ prefix and follow a consistent verb_noun pattern: list_models, get_credits, upscale_image, upscale_video, get_job. This makes the tool set predictable and easy to navigate.
Five tools is a well-scoped set for an upscaling API: model discovery, quota monitoring, two job submission variants, and job status/result retrieval. Each tool earns its place without redundancy.
The core workflow is fully covered: list available models, submit image or video jobs from public URLs, poll job status, and retrieve results. There are no obvious dead ends or missing operations required for the primary use case.