Skip to main content
Glama
Sign In
Clipwright

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Approve a workflow revision

approve_workflow_plan

Approve a specific workflow plan revision and content digest after reviewing warnings; this records approval only and does not start a run or paid launch.

Instructions

Explicitly approve the chosen plan revision and content_digest. Free; it stores approval but starts no run. Read all issues and warnings first. Take revision and content_digest from the plan answer. Approval is separate from a quote and a paid launch.

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": {
      "plan_id": "<plan_id>",
      "revision": "<revision>",
      "content_digest": "<content_digest>"
    },
    "name": "approve_workflow_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes
revisionYes
content_digestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.39.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / revision / maximum
      Removed value: -9007199254740991
  2. Addedv0.29.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare it as a non-destructive write; the description adds the crucial facts that it is free and that it does not trigger execution. It does not cover idempotency, whether a prior approval can be superseded, or what happens on a digest mismatch.

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?

Four short sentences, front-loaded with the action and its key constraint (no run started), then prerequisites, then disambiguation. No filler or repetition of schema facts.

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 three-required-parameter mutation with no output schema, the definition covers cost, side effects, prerequisites, and parameter provenance. The remaining gaps are edge-case behavior (mismatched digest, re-approval) rather than anything blocking a correct call.

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 0%, so the description must carry the burden. It tells the agent where to source two of three parameters ('from the plan answer') but gives no meaning for plan_id or the expected digest/revision formats beyond what the JSON patterns already enforce.

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 and resource ('approve the chosen plan revision and content_digest') and immediately separates it from the adjacent siblings: 'stores approval but starts no run,' versus quote_workflow_plan and run_workflow_plan. An agent can pick it out of the sibling list without opening either schema.

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?

Gives prerequisites ('read all issues and warnings first') and value provenance ('take revision and content_digest from the plan answer'), plus sequencing against quote and paid launch. It never states an explicit do-not-call condition, so it falls just short of a full 5.

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

Deploy Server

Other Tools