No user-submitted related servers found.
Scored across 3 tools
Each tool has a clearly distinct target: list_history reads past generations, list_models reads available models/hardware, and generate creates a new image. The two list_* tools differ in resource domain (history vs. models), so misselection is unlikely.
Two tools follow a clean verb_noun pattern (list_history, list_models), while generate is a bare verb without a noun object. This is a minor deviation but still readable and predictable overall.
Three tools is lean but each earns its place: generation, model discovery, and history review cover the essential loop of a focused image studio. It sits at the low end, but nothing feels redundant or missing from the core scope.
The core workflow (discover models → generate → review history) is covered, and images are returned via ResourceLink/ImageContent. However, there is no way to fetch a specific history entry, delete or prune history, or check status of a long-running generation, leaving notable gaps.