Skip to main content
Glama

Postprocess Clarity Snapshot

postprocessClaritySnapshot

Re-run postprocessing agents on an existing v2 clarity snapshot. Targets either the current-process snapshot or the automation proposal snapshot, identified by id in the body. Flips the process status to generating and returns 202 immediately; agents run asynchronously and flip the status back to review once they settle.

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": {
      "process_id": "<process_id>",
      "type": "<type>"
    },
    "name": "postprocessClaritySnapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe snapshot kind to post-process.
scopeNoOnly accepted when type is `current_process`. `missing_info` re-runs only the missing-info agent, on the live current process.
process_idYesThe clarity process id
current_process_idNoRequired when type is `current_process`.
transformation_proposal_idNoRequired when type is `transformation_proposal`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scope
      Added value: +{
      +  "description": "Only accepted when type is `current_process`. `missing_info` re-runs only the missing-info agent, on the live current process.",
      +  "enum": [
      +    "all",
      +    "missing_info"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses real side effects: the process status flips to `generating`, a 202 is returned immediately, and the status returns to `review` once the async agents settle. That async/state-machine behaviour is exactly the kind of context annotations cannot convey. It doesn't mention preconditions (e.g. snapshot must already exist, or what happens if a run is already in flight), which keeps it from a 5.

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?

Three sentences, front-loaded with the action, then targeting, then runtime behaviour. Every sentence carries distinct information with no repetition of the name or title.

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 an async mutation with no output schema, this is nearly complete: the caller learns the immediate response (202), that work continues in the background, and the terminal status. The only omission is failure/precondition behaviour, such as what occurs if the snapshot is not in a re-runnable state.

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 meaning of `type`, `scope`, `process_id`, `current_process_id` and `transformation_proposal_id` is already carried by the schema. The description only restates that targeting happens via id in the body and mentions the two `type` values; it adds nothing about `scope` or the conditional-required id parameters, so the baseline 3 applies.

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 gives a specific verb plus resource ('Re-run postprocessing agents on an existing v2 clarity snapshot') and names the two snapshot kinds it can target, which separates it from the plain 'generate'/'save' snapshot siblings. It stops short of explicitly distinguishing itself from the closest alternatives like generateClarityProcessSnapshot or bulkGenerateClarityProcessSnapshots, so the agent must infer that this acts on an already-existing snapshot.

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 implied fairly clearly: use this when an existing snapshot needs its agents re-run, not when creating a snapshot. However, it never states when NOT to use it, nor points to the sibling to use instead when the snapshot does not exist yet or when a fresh generation is wanted.

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