No user-submitted related servers found.
Scored across 30 tools
Every single tool exists twice with byte-identical descriptions: `figcraft_create_and_open` and `create_and_open`, `figcraft_batch` and `batch`, etc. An agent has no principled way to choose between the prefixed and unprefixed variants — they appear to do exactly the same thing. This is the maximal case of overlapping tools.
Individually the names follow a clean `verb_noun` snake_case pattern (create_node, set_properties, audit_layout). However the surface uses two parallel naming conventions simultaneously — a `figcraft_`-prefixed alias set and a bare alias set — with no stated rule for which to use, which is exactly the kind of mixed convention this dimension penalizes.
The count is reported as 30, well past the 25+ threshold for 'too many', and in reality there are only ~15 unique operations duplicated 2x. The extra 15 tools earn no place in the surface and actively inflate the tool list an agent must scan.
The unique tool set covers the full canvas lifecycle for a Figma-like editor: create/open, node creation, autolayout, components, property mutation, theming, overflow repair, layout audit, document inspection, screenshot, save, and a generic `batch` escape hatch. Minor gaps exist (no explicit delete/remove-node, reorder, or grouping tool outside of batch), but these are workable.