Skip to main content
Glama

Remove a pipeline

dosai_archive_pipeline
Destructive

Remove (archive) a pipeline. Refused while it has open deals: move or close them first. Two steps: the first call only says what will happen.

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": {
      "workspace_id": "<workspace_id>",
      "pipeline_id": "<pipeline_id>"
    },
    "name": "dosai_archive_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pipeline_idYes
workspace_idYesCRM project (workspace) id, as returned by dosai_list_workspaces.
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed2 schema fields changed
    • removedInput schema / properties / pipeline_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / workspace_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds genuine context on top: the open-deals refusal condition and the fact that the first call is a no-op that only previews the effect. It omits whether an archived pipeline can be restored and what happens to its associated data, so it is strong but not complete.

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 short sentences, front-loaded with the action, then the blocking condition, then the call sequence. The preview sentence lightly overlaps the confirm_token schema text but still earns its place at the tool level by telling the agent the first call is an intentional dry run.

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?

With three parameters and no output schema, the description covers the essential behavior: destructive intent, the precondition that blocks it, and what the first call returns (a preview plus a code). It leaves the second call's return value and post-archive consequences unstated, a modest gap for a destructive 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?

Schema coverage is 67% and the two documented parameters (workspace_id, confirm_token) already carry detailed descriptions, including the full two-step confirmation protocol. The description adds no new meaning about pipeline_id, the one undocumented parameter, so it does not compensate for the remaining coverage gap. 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 opens with a specific verb+resource pair, 'Remove (archive) a pipeline', and the parenthetical 'archive' usefully pins the semantics as a soft removal rather than a hard delete, which separates it from dosai_create_pipeline and dosai_update_pipeline. It stops short of explicitly naming the sibling it contrasts with, so it lands just below the top mark.

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?

It states a real precondition ('Refused while it has open deals: move or close them first') and frames the required two-call pattern, so an agent knows both when the call will fail and how to sequence it. It does not name an alternative tool (e.g. update/close-deals path) for the case where the refusal fires, which is the only missing guidance.

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