No user-submitted related servers found.
Scored across 8 tools
The tools map cleanly onto distinct workflow stages (catalog lookup, schema, validation, form fill, resume, download, status, close). The only real risk is portal_ausfuellen versus ausfuellen_fortsetzen, which share the filling purpose, but the description explicitly gates the latter on status 'gericht_bestaetigen'. kataloge_suchen and antrag_schema both return metadata but for clearly different purposes.
All names are lowercase snake_case following the German object_verb convention (kataloge_suchen, antrag_pruefen, portal_ausfuellen, eda_herunterladen, portal_schliessen). Two tools are noun_noun (antrag_schema, portal_status) and one inverts the order (ausfuellen_fortsetzen), which are minor deviations that remain readable.
Eight tools is well-scoped for a single guided workflow: lookup, schema, validate, fill, resume, fetch, inspect, close. Each has a clear place and none appears redundant boilerplate.
The lifecycle is nearly closed: schema discovery, catalog lookup, pre-validation, portal filling with an explicit human-confirmation breakpoint, resume, file download, status polling and teardown. Minor gaps: there is no explicit tool to open/start a portal session (implicitly bundled into portal_ausfuellen) and no separate way to surface detailed portal error listings beyond portal_status, though agents can work around both.