No user-submitted related servers found.
Scored across 1 tool
With only one tool there is literally no opportunity for misselection, so the set cannot be ambiguous across tools. However, the single tool's own purpose is dense and opaque (catalog/guide/search/describe/execute/batch/rpc/native all funneled through one entry point), which makes its scope hard to pin down.
There is no set of names to compare, so no inconsistency exists, but 'art' is a bare noun that establishes no verb_noun convention and is vague about what it does. It is readable but not descriptive of the underlying dispatch behavior.
A single tool is far too few for a server that apparently fronts an entire ArtCraft/vendor CLI with catalog, search, describe, execute, batch, and rpc surfaces. Everything is collapsed into one catch-all entry, forcing the agent to guess subcommands rather than choose a tool.
The description implies coverage of all native CLI functions plus a resources/prompts rpc bridge, so capability may exist behind the single tool. But the surface itself exposes no discrete, discoverable operations, leaving the agent dependent on self-describing catalog/guide steps to reach coverage.