Skip to main content
Glama

Update Clarity Process

updateClarityProcess
Destructive

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "updateClarityProcess"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesClarity process id
nameNoNew process name
statusNoMark a review-stage process complete, or reopen a completed process for review
visibilityNoProcess visibility within the team
mapLanguageNoLanguage Duvo writes this process's map in, or null to use the team's map language
customPromptNoProcess-specific guidance, or null to clear it
showMissingInfoNoShow missing-info questions on the map, or null to follow the team default
missingInfoGuidanceNoTopics to prioritize in this process's missing-info review. Send null to clear.
showFieldsAndActionsNoShow fields and actions on the map, or null to follow the team default
independentInterviewsNoRun each interview independently: no briefing from earlier interviews and a neutral opener

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / missingInfoGuidance
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 5000,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Topics to prioritize in this process's missing-info review. Send null to clear."
      +}
    • addedInput schema / properties / showFieldsAndActions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Show fields and actions on the map, or null to follow the team default"
      +}
    • addedInput schema / properties / showMissingInfo
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Show missing-info questions on the map, or null to follow the team default"
      +}
  2. Changed1 schema field changed
    • 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"
      +}
  3. Changed2 schema fields changed
    • 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"
      +]
  4. Changed1 schema field changed
    • addedInput schema / properties / independentInterviews
      Added value: +{
      +  "description": "Run each interview independently: no briefing from earlier interviews and a neutral opener",
      +  "type": "boolean"
      +}
  5. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety bar is partly covered. The description adds substantive context the annotations cannot: a three-tier permission model tied to specific field groups, which directly affects whether a call will succeed. It does not explain what the destructive behavior actually does (e.g., whether clearing guidance via null is recoverable or whether map settings changes trigger regeneration).

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 sentences, no filler, with the operation and its field scope front-loaded before the permission constraints. The second sentence is dense but structured as parallel clauses, so it reads as necessary information rather than padding.

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

Completeness3/5

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

For a 10-parameter destructive mutation with no output schema, the description covers purpose and authorization well. It omits partial-update semantics (whether omitted fields are left untouched), what the response looks like, and side effects such as whether changing mapLanguage rewrites an existing map — gaps an agent would care about before calling.

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 coverage is 100% and each of the 10 parameters is individually documented, so the baseline is 3. The description adds value by grouping fields under permission tiers (e.g., visibility vs. status have different role requirements), but it does not restate null semantics or defaults that the schema already covers.

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?

The description opens with a specific verb and resource and enumerates the exact editable fields (name, guidance, interview independence, map settings, visibility, completion status), which lets an agent map intent to this tool. It stops short of differentiating from close siblings such as updateClarityProcessSharing or updateClarityGuidance, whose domains overlap with 'visibility' and 'guidance' here.

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?

It gives concrete role conditions for each field group (Team Builders for names/guidance/map settings, creator or team manager for visibility, Lead Builder for complete/reopen), which is real usage guidance. However, there is no guidance on when to choose this tool over the sibling update tools that touch overlapping fields, leaving tool selection partly to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources