Skip to main content
Glama

Duvo MCP

by io.github.duvoai

Update Clarity Process Link

updateClarityProcessLink

Update a process-to-process link in the organization's Clarity landscape when the caller can manage both endpoint teams.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoRelationship type between the source process node and target process node
orgIdYes
stateNoWhether the link is suggested by Duvo or confirmed by a user
confidenceNoConfidence score from 0 to 1, or null to clear it
source_node_idNoReplacement hierarchy node id for the source process
target_node_idNoReplacement hierarchy node id for the target process
process_link_idYesUnique process-link identifier

TDQS

A4.2/5.0
Behavior4/5

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

Annotations are present but only provide hints (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds valuable behavioral context beyond these hints by stating the authorization requirement ('can manage both endpoint teams'), which is not derivable from the annotations. It does not delve into side effects, but that is less critical given the annotations clarify safety.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that states the action, resource, and a key condition without any unnecessary words. It is concise and immediately informative.

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?

Given the tool has 7 parameters with rich schema descriptions and no output schema, the description covers the essential purpose and a critical permission gate. It does not explain the broader domain (e.g., what a Clarity landscape is), but that is likely obvious from the tool name and sibling context. The description is sufficient for an agent to understand when to invoke the tool.

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?

The schema description coverage is 86% (6 of 7 parameters have descriptions), so the schema already provides robust parameter semantics. The description text itself adds no parameter-specific meaning, only the general context. Per the rubric, the baseline for high schema coverage is 3, and the description does not raise it.

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

Purpose5/5

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

The description uses a specific verb ('Update') and a clear resource ('a process-to-process link in the organization's Clarity landscape'), which distinguishes it from sibling tools like createClarityProcessLink, deleteClarityProcessLink, or listClarityProcessLinks. It also adds a condition about managing endpoint teams, giving precise scope.

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

Usage Guidelines4/5

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

The description clearly implies the context for use (updating an existing process link) and includes a relevant prerequisite ('when the caller can manage both endpoint teams'). It does not explicitly name alternatives or exclusions, but the context is unmistakable given the sibling tool names.

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

All Duvo MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

Despite detailed descriptions, many tool names are highly ambiguous, with multiple tools covering the same conceptual actions (e.g., acceptClarityCaptureSuggestion vs. acceptClarityTeamAssignmentSuggestion, or the many deleteClarity*Interview tools). The set is so large that distinguishing between, say, listClarityFolders, listClarityProcesses, and listClarityProcessSummaries requires reading deep into descriptions, reducing agent selection accuracy.

Naming Consistency4/5

The naming convention is predominantly verb_noun (e.g., createClarityProcess, listAgents, deleteQueue), and is remarkably consistent across the 316 tools. There are only minor deviations, such as 'fileSuggestedClarityProcesses' (verb + adjective noun) and 'bulkUpdateCasePriority' (where 'bulk' could be seen as a prefix), but overall the pattern holds strongly.

Tool Count1/5

With 316 tools, this server is extremely oversized for any single agent to manage effectively. The massive number of tools suggests poor modularization—many of these tools likely belong in separate, smaller servers focused on specific domains (e.g., Clarity, Pulse, Agent management). The cognitive load for an agent to choose from 316 options is very high, leading to frequent misselection.

Completeness4/5

The tool surface covers an extraordinarily wide range of operations across the Duvo platform: agents, runs, cases, queues, Clarity processes, skills, integrations, notifications, teams, and more. Most resource types have full CRUD and lifecycle management. Notable minor gaps exist (e.g., no tools for managing specific notification batch severities dynamically, and some interview management is missing batch operations), but for the platform's scope, coverage is impressively thorough.

Resources