Duvo MCP

Update Clarity Process

updateClarityProcess

Destructive

Update a Clarity process name, guidance, interview independence, visibility, or completion status. Team Builders can edit names, guidance, and interview independence, only the creator or a team manager can change visibility, and completing or reopening a process for review requires a Lead Builder role.

Input Schema

Name	Required	Description
`id`	Yes	Clarity process id
`name`	No	New process name
`status`	No	Mark a review-stage process complete, or reopen a completed process for review
`visibility`	No	Process visibility within the team
`mapLanguage`	No	Language Duvo writes this process's map in, or null to use the team's map language
`customPrompt`	No	Process-specific guidance, or null to clear it
`independentInterviews`	No	Run each interview independently: no briefing from earlier interviews and a neutral opener

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / mapLanguage

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "cs",
+        "de",
+        "de-CH",
+        "en",
+        "en-GB",
+        "es",
+        "es-MX",
+        "fr",
+        "hu",
+        "pl",
+        "pt",
+        "pt-BR",
+        "sk",
+        "sl",
+        "th",
+        "uk",
+        "ar-EG",
+        "ar-SA",
+        "da-DK",
+        "de-AT",
+        "el-GR",
+        "en-AU",
+        "en-GB-scotland",
+        "en-IE",
+        "en-IN",
+        "en-NG",
+        "en-ZA",
+        "es-AR",
+        "fi-FI",
+        "fr-BE",
+        "fr-CA",
+        "gsw-CH",
+        "he-IL",
+        "hi-IN",
+        "hi-Latn-IN",
+        "id-ID",
+        "it-IT",
+        "ja-JP",
+        "ko-KR",
+        "nb-NO",
+        "nl-BE",
+        "nl-NL",
+        "ro-RO",
+        "sv-SE",
+        "tr-TR",
+        "vi-VN",
+        "yue-HK",
+        "zh-Hans-CN",
+        "zh-Hant-TW",
+        "af-ZA",
+        "ak-GH",
+        "sq-AL",
+        "am-ET",
+        "hy-AM",
+        "as-IN",
+        "az-AZ",
+        "eu-ES",
+        "be-BY",
+        "bn-BD",
+        "bs-BA",
+        "bg-BG",
+        "my-MM",
+        "ca-ES",
+        "ceb-PH",
+        "hr-HR",
+        "et-EE",
+        "fo-FO",
+        "fil-PH",
+        "gl-ES",
+        "ka-GE",
+        "gu-IN",
+        "ha-NG",
+        "is-IS",
+        "ga-IE",
+        "kn-IN",
+        "kk-KZ",
+        "km-KH",
+        "rw-RW",
+        "ku-TR",
+        "ky-KG",
+        "lo-LA",
+        "lv-LV",
+        "lt-LT",
+        "mk-MK",
+        "ms-MY",
+        "ml-IN",
+        "mt-MT",
+        "mi-NZ",
+        "mr-IN",
+        "mn-MN",
+        "ne-NP",
+        "or-IN",
+        "om-ET",
+        "ps-AF",
+        "fa-IR",
+        "pa-IN",
+        "qu-PE",
+        "rm-CH",
+        "ru-RU",
+        "sr-RS",
+        "sd-PK",
+        "si-LK",
+        "so-SO",
+        "st-ZA",
+        "sw-TZ",
+        "tg-TJ",
+        "ta-IN",
+        "te-IN",
+        "tn-ZA",
+        "tk-TM",
+        "ur-PK",
+        "uz-UZ",
+        "cy-GB",
+        "fy-NL",
+        "wo-SN",
+        "yo-NG",
+        "zu-ZA",
+        "bn-IN",
+        "ur-IN",
+        "fr-CH",
+        "it-CH",
+        "de-BE",
+        "sw-KE",
+        "sw-UG",
+        "ms-SG",
+        "zh-Hans-SG",
+        "ta-SG",
+        "ta-LK",
+        "yue-CN",
+        "ar-IL",
+        "ar-MA",
+        "fr-MA",
+        "sv-FI",
+        "es-US",
+        "ru-BY",
+        "ru-KZ",
+        "fa-AF",
+        "ar-DZ",
+        "fr-DZ",
+        "ar-TN",
+        "fr-TN",
+        "ar-LY",
+        "ar-SD",
+        "ar-IQ",
+        "ku-IQ",
+        "ar-SY",
+        "ar-JO",
+        "ar-AE",
+        "ar-QA",
+        "ar-KW",
+        "ar-OM",
+        "ar-YE",
+        "ar-LB",
+        "fr-LB",
+        "pt-AO",
+        "pt-MZ",
+        "es-CO",
+        "es-PE",
+        "es-CL",
+        "es-VE",
+        "es-EC",
+        "es-BO",
+        "qu-BO",
+        "es-PY",
+        "es-UY",
+        "es-CU",
+        "es-GT",
+        "es-HN",
+        "es-NI",
+        "es-CR",
+        "es-PA",
+        "es-DO",
+        "es-SV",
+        "sr-ME",
+        "fr-CD",
+        "fr-CI",
+        "fr-SN",
+        "fr-ML",
+        "fr-CM",
+        "da-GL",
+        "tn-BW",
+        "af-NA",
+        "el-CY",
+        "tr-CY",
+        "fr-LU",
+        "de-LU",
+        "en-CA",
+        "en-NZ",
+        "en-SG",
+        "en-PH",
+        "en-KE",
+        "en-GH",
+        "en-PK"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Language Duvo writes this process's map in, or null to use the team's map language"
+}

Changed2 schema fields changedOct 19, 2026

changedInput schema / properties / status / description

Previous value: -"Mark a review-stage process complete"New value: +"Mark a review-stage process complete, or reopen a completed process for review"

changedInput schema / properties / status / enum

Previous value: -[
-  "complete"
-]New value: +[
+  "complete",
+  "review"
+]

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / independentInterviews

Added value: +{
+  "description": "Run each interview independently: no briefing from earlier interviews and a neutral opener",
+  "type": "boolean"
+}

AddedAug 18, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations supply readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the safety profile is known; the description adds real value on top by disclosing the per-field authorization model (who can change names/guidance/interview independence vs. visibility vs. status). It does not explain that omitting fields leaves them unchanged or that passing null clears guidance, which matters for a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences: the operations come first, then the authorization rules as a parallel clause. No filler, though the second sentence is dense enough to require a careful read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 7-parameter mutation with no output schema, the definition covers scope and authorization adequately. Partial-update semantics (unspecified fields untouched, null clears customPrompt/mapLanguage) and the consequences of status transitions are left to the schema, which mostly carries them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented, including customPrompt's null-to-clear semantics and mapLanguage's null fallback. The description maps facets to roles, which adds permission meaning, but it omits mapLanguage from its field list and introduces no syntax or format detail the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (update) and resource (Clarity process) and enumerates the editable facets: name, guidance, interview independence, visibility, completion status. That is enough to distinguish it from generic siblings, though it never clarifies its boundary against near-neighbors like updateClarityProcessSharing (which also touches visibility/share scope) or updateClarityGuidance (guidance also settable here via customPrompt).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is framed entirely as role permissions (Team Builder, creator/team manager, Lead Builder), which is genuinely useful gating but tells the agent who may call it, not when to prefer it. With updateClarityProcessSharing and updateClarityGuidance in the sibling list, the description should say which tool owns sharing/guidance changes; that ambiguity is left unresolved.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Duvo MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?