Automatic Video Mosaic & Masking MCP (동영상 모자이크), Restore Original — NoonAI DIS

Most tools target a distinct resource+action (upload, submit, poll status, fetch result metadata, download, billing). The one real overlap is encrypt_image/encrypt_video versus submit_encrypt_job, which are one-shot wrappers around the same underlying job flow; the descriptions do explicitly explain the distinction, which mitigates but does not eliminate the confusion. The three job-result-ish tools (get_job_status, get_job_result, download_job_result) are separable but demand careful reading.

Almost everything follows snake_case verb_noun conventions (get_job_status, upload_file, purchase_credits, register_billing_payment_method). The only wrinkle is that 'encrypt' is used as an action verb in encrypt_image/encrypt_video but as a noun modifier in submit_encrypt_job/get_encrypt_constraints, a minor semantic inconsistency rather than a formatting one.

Fifteen tools is a reasonable size for an upload→submit→poll→download pipeline, and each core-flow tool earns its place. However, six of the fifteen are billing/account tools (status, pricing, usage, purchase x2, register payment method), which is heavy for what is nominally an anonymization server and dilutes the surface.

The full lifecycle is covered end to end: upload (path or base64), constraints/policy lookup, submit, poll, fetch result, download, plus one-shot image/video shortcuts and billing. Missing pieces are minor but real: no cancel/delete job, no asset deletion, and no proper job listing with statuses (get_usage_summary only returns ULIDs), which could leave an agent stuck on cleanup or batch discovery.