Related Servers

The 10 vision/from_* tools are essentially duplicate or near-duplicate aliases of each other (vision_from_file vs from_file, vision_from_files vs from_files, etc.), creating massive ambiguity. An agent cannot reliably distinguish which tool to pick when 12 of 15 tools describe the same core operation of 'describe files/resources with Gemini'.

There is a somewhat consistent pattern within the vision_from_* family (file/files/files_mixed, resource/resources/resources_mixed), but the alias tools (from_file, from_files, etc.) and the duplicate prefix 'vision_from_' broken by short aliases create two inconsistent naming conventions. The mix of descriptive prefixes with abbreviated aliases, plus session management tools (new_vision, compact) that don't follow the pattern, makes naming inconsistent overall.

15 tools is within the borderline range, but roughly two-thirds of them are redundant aliases of the same 5-6 core operations. The effective distinct tool surface is only about 5 unique operations inflated to 15, making the count feel padded rather than well-scoped.

The core input variants (single vs multiple, file vs resource, mixed types) are covered, and session management (reset, compact, usage stats) is present. However, there are no tools for more advanced capabilities like providing prompts/instructions to the vision model, and the heavy alias duplication obscures whether genuinely useful operations are missing.