No user-submitted related servers found.
Scored across 9 tools
The agreement tools are split by action (create/get/list/update_status/render/checklist) and the license tools are clearly separate, so an agent can usually pick the right one. The only mild ambiguity is that agreement_create and agreement_render both produce Markdown output, while agreement_checklist could be mistaken for a validation step rather than a read-only check.
Most tools follow an agreement_<verb pattern, and license_status/license_activate keep the same convention. The exceptions are agreement_checklist and clause_library, which use nouns instead of actions, creating a small but noticeable deviation.
Nine tools is well-scoped for a service-agreement server: CRUD-like agreement operations, rendering, checklist validation, a clause library, and license management all earn their place. The count feels intentional rather than bloated or sparse.
The set covers creating, reading, listing, status transitions, rendering, validation, clause lookup, and license activation, so the main lifecycle is represented. A clear gap is the absence of any way to update an agreement's content after creation; agents cannot fix a mistake or revise terms without creating a new agreement.
