Related Servers

There are several functional clusters with real overlap — four search tools (search, search_content, search_natural, search_by_name), three task tools (get_status, wait, update), and two overlapping document-text tools (get_text vs get_edoc mode=text). However, the descriptions are unusually explicit about routing between siblings, so an agent can reliably pick the right one in each case.

Tool names follow a steady laserfiche_<resource>_<action> pattern (entry_get, folder_list, field_values_get, template_field_list, task_get_status), with only minor deviations like the compound entry_search_by_name / document_find_duplicates and the task_* verb trio. The one wrinkle is that descriptions internally reference tools by a different convention (get_entry, list_folder, set_tags), but the actual catalog names themselves are consistent.

At 23 tools this sits in the heavy band for a document-management server. The breadth (repositories, fields, tags, templates, links, audit reasons, four search modes, four document accessors, three task polls) is largely justified, but the redundant task_get_status/wait/update trio and the four search variants make it slightly bloated rather than tight.

Read/query coverage is strong and near-complete: entry metadata, path resolution, folder listing, comparison, four search modes, document text/edoc/image access, duplicate detection, all definition lookups, and full async task lifecycle. The notable gap is that no mutation tools (create/update/delete entries, set fields/tags/links, assign templates) appear in this catalog, even though descriptions reference them — likely a read-only scope, but a dead end for write workflows.