No user-submitted related servers found.
Scored across 2 tools
The two tools have clearly distinct purposes: listing available blueprints versus downloading a specific blueprint by ID. There is no overlap or ambiguity, as one provides an overview and the other retrieves a detailed artifact.
Both tool names follow a consistent verb_noun pattern: 'list_blueprints' and 'get_blueprint'. This makes the API predictable and easy to reason about.
With only two tools, the surface is minimal but aligns with a read-only catalog service. It borders on thin, but the scope is narrow—listing and retrieving blueprints—so the count is acceptable though not rich.
The lifecycle for a catalog is complete: list and get cover discovery and retrieval. There's no need for update/delete since blueprints are static free resources. Minor gaps like search or filter are absent, but the core workflow is fully supported.
