Related Servers

Many tools have overlapping boundaries: busqueda_universal, consulta_maestra, caso_ejecutar and agent_run all perform broad multi-source consultation, and there are 9+ graph tools (grafo_ver_corpus, grafo_ver_caso, generar_grafo_vinculos, graphify_resumen_comunidades, graphify_consulta_subgrafo, graphify_trazar_camino, graphify_explicar_institucion, graphify_analizar_impacto, graphify_god_nodes) with fuzzy distinctions. Similarly, doctrina_*, graphify_* and pjud_* families overlap heavily, and six SII tools (sii_search_circulares, sii_buscar_resoluciones_y_oficios, sii_oficios_por_anio, sii_jurisprudencia_judicial, sii_actos_regionales) are hard to tell apart. Rich descriptions help somewhat but cannot resolve the deep functional overlap.

The set mixes Spanish and English, prefix-first and verb-first conventions with no predictable pattern: bcn_get_ley, pjud_search_jurisprudencia, caso_analizar, grafo_ver_corpus, generar_documento, busqueda_universal, consulta_maestra, agent_run, notebooklm_create_notebook. Prefix groupings (bcn_, sii_, graphify_, doctrina_) coexist with verb-first and noun-first Spanish names, making the naming unpredictable.

With 87 tools this is an extreme mismatch for any single server surface; even a broad legal-research domain cannot justify this many tools without severe fragmentation. Many tools are sub-variants of one another (SII family, graph family, generator family), indicating the surface is far heavier than necessary.

Coverage is genuinely broad — norms (BCN historical and current), jurisprudence (PJUD, TC, CGR, DT, TDLC, CMF, SMA, tribunals ambientales), doctrine, document generation, OCR, agents and graphs — so most legal workflows have a path. Minor gaps remain (e.g. dedicated criminal/family case tools beyond clinica_intake_social), but the surface is close to complete for the stated purpose.