No user-submitted related servers found.
Scored across 58 tools
Most tools target a distinct resource+action, but the video-generation cluster (flow_gerar_video, flow_roteiro, flow_video_longo, flow_estender_video) and the Studio cluster (notebook_gerar_* × 10, notebook_estudio / _status / _baixar) overlap enough that an agent must read long descriptions to pick correctly. Similarly notebook_perguntar / notebook_resposta / notebook_conversa / notebook_pesquisar_fontes are separable only via detailed prose. Descriptions do resolve most confusion, but the boundaries are not self-evident from names alone.
All snake_case with clear domain prefixes (notebook_, flow_, login_), which aids grouping. However word order within names is inconsistent: verb-first forms (notebook_listar, flow_gerar_video) mix with noun-first forms (notebook_fonte_remover, notebook_nota_criar, notebook_estudio_baixar, flow_personagem_criar). Also two non-prefixed tools (login_*, diagnostico — the latter with no prefix at all) break the pattern.
58 tools is far beyond a comfortable surface and forces the agent to scan a large catalog for each request; ~10 Studio generation tools plus ~20 Flow tools plus NotebookLM CRUD create a heavy menu. The domain is genuinely broad (NotebookLM + Flow + Drive + auth/diagnostics), so it is not an arbitrary mismatch, but the count still needs consolidation (e.g. one Studio generator with a type parameter).
Coverage is exceptional: create/list/rename/delete for notebooks, sources, notes, Studio items, Flow projects and characters, plus generation, status polling, re-download, Drive export, credit/cost accounting, login and self-diagnostics. Async long-running work, quota ceilings and timeout fallbacks all have dedicated tools, so agents have no dead ends.