Skip to main content
Glama

Duvo MCP

by io.github.duvoai
OverviewDiscussionsAdmin

Generate Clarity Process Snapshot

generateClarityProcessSnapshot

Trigger a snapshot generation pipeline for a v2 clarity process, selected by kind. current_process runs the generateCurrentProcess pipeline (body fields are proposal-only and rejected); transformation_proposal runs the generate or regenerate proposal pipeline. Returns 202 immediately and finalises asynchronously via the cc-server webhook stream.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesSnapshot kind to list
process_idYesThe clarity process id
custom_guidanceNoAutomation proposals only: optional freeform guidance for this generation. Used as high-priority design guidance, not source-of-truth evidence.
regenerate_fromNoAutomation proposals only: id of a prior proposal snapshot to refine. When supplied, runs the regenerate pipeline using that proposal's current-process snapshot as the anchor and the extra captures collected since.
source_snapshot_idNoAutomation proposals only: id of the current-process snapshot to anchor the new proposal to. Defaults to the latest snapshot for the process.
transformation_aggressivenessNoTransformation proposals only: the transformation appetite. `aggressive`, `conservative`, and `none` redesign around Duvo automation with decreasing freedom to change the process; `optimize` standardizes and streamlines the process while every step stays performed by people.aggressive

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / transformation_aggressiveness / description
      Previous value: -"Automation proposals only: controls how much the generated proposal should change the current process structure."New value: +"Transformation proposals only: the transformation appetite. `aggressive`, `conservative`, and `none` redesign around Duvo automation with decreasing freedom to change the process; `optimize` standardizes and streamlines the process while every step stays performed by people."
    • changedInput schema / properties / transformation_aggressiveness / enum
      Previous value: -[
-  "none",
-  "conservative",
-  "aggressive"
-]New value: +[
+  "none",
+  "conservative",
+  "aggressive",
+  "optimize"
+]
  2. Changed4 schema fields changed
    • changedInput schema / properties / custom_guidance / description
      Previous value: -"Transformation proposals only: optional freeform guidance for this generation. Used as high-priority design guidance, not source-of-truth evidence."New value: +"Automation proposals only: optional freeform guidance for this generation. Used as high-priority design guidance, not source-of-truth evidence."
    • changedInput schema / properties / regenerate_from / description
      Previous value: -"Transformation proposals only: id of a prior proposal snapshot to refine. When supplied, runs the regenerate pipeline using that proposal's current-process snapshot as the anchor and the extra captures collected since."New value: +"Automation proposals only: id of a prior proposal snapshot to refine. When supplied, runs the regenerate pipeline using that proposal's current-process snapshot as the anchor and the extra captures collected since."
    • changedInput schema / properties / source_snapshot_id / description
      Previous value: -"Transformation proposals only: id of the current-process snapshot to anchor the new proposal to. Defaults to the latest snapshot for the process."New value: +"Automation proposals only: id of the current-process snapshot to anchor the new proposal to. Defaults to the latest snapshot for the process."
    • changedInput schema / properties / transformation_aggressiveness / description
      Previous value: -"Transformation proposals only: controls how much the generated proposal should change the current process structure."New value: +"Automation proposals only: controls how much the generated proposal should change the current process structure."
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Discloses critical runtime behavior beyond annotations: 'Returns 202 immediately and finalises asynchronously via the cc-server webhook stream' and notes that body fields are proposal-only and rejected for `current_process`. Annotations (readOnlyHint=false, idempotentHint=false) give little context, so this description carries the transparency burden and largely fulfills it.

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?

Two dense sentences with the core action front-loaded in the first sentence and async behavior in the second. No filler; every sentence earns its place.

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 trigger tool with no output schema, it covers pipeline selection, async handoff, and field restrictions, which is sufficient. Minor omission: no mention of how to correlate the eventual webhook event back to this invocation, but that is not required to call the tool correctly.

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 the schema already documents each parameter. The description adds a useful note about proposal-only fields being rejected, but does not restate syntax, enums, or constraints. Thus it only marginally supplements what the schema already provides.

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?

States a specific verb ('Trigger'), resource ('snapshot generation pipeline for a v2 clarity process'), and disambiguates two kinds with distinct pipelines (`current_process` vs `transformation_proposal`). Clearly distinguishes this generation action from sibling save/get/promote/revert snapshot tools.

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?

Clearly explains the two kind options and the triggers for each (generateCurrentProcess vs generate/regenerate proposal), including the fact that `current_process` rejects proposal-only fields. However, it does not explicitly contrast this tool with sibling tools like `getClarityProcessSnapshot` or `saveClarityProcessSnapshot`, so alternative selection is inferred rather than explicit.

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
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