No user-submitted related servers found.
Scored across 15 tools
Most tools map to clearly distinct resource-action pairs, but the adaptation and approval cluster (adapt_preview, adaptation_diff, variant_revise, approval_pack, approve_variant, approval_check) has subtle boundaries that rely heavily on the descriptions. An agent can tell them apart, but several are close enough that misselection is plausible without careful reading.
All names use snake_case, but the structural convention is mixed: noun_verb (content_ingest, content_get, variant_revise, account_set, policy_check), verb_noun (adapt_preview, approve_variant), and noun_noun compounds (approval_pack, adaptation_diff, engagement_report, receipt_list). It remains readable, but there is no single predictable pattern.
Fifteen tools fit a multi-stage governance domain involving content lifecycle, adaptation, approval, accounts, engagement policy, kill switches, and receipts. Each tool maps to a distinct operation in that pipeline, and none appears to be filler.
Core ingest/get, adaptation, approval, account, policy, and receipt operations are covered, but there is no list/search capability for canonical content or variants and no direct variant_get. Agents must know content or variant IDs out-of-band, which is a notable discovery gap for an otherwise lifecycle-oriented toolset.