Skip to main content
Glama

Rename a pipeline or change its stages

dosai_update_pipeline
Destructive

Change a pipeline's name, description or stages. Pass stages as the WHOLE new list (3-15, open stages first, then one won and one lost); keep an existing stage by its id. A stage you leave out is removed: say where its deals go in removals. Only what you pass changes. Admin or owner.

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_update_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
stagesNo
removalsNoRemoved stage id and the stage its deals move to.
descriptionNo
pipeline_idYes
workspace_idYesCRM project (workspace) id, as returned by dosai_list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / stages / items / properties / off_path
      Added value: +{
      +  "description": "Side stage (e.g. «No-show»): outside the main path, reports count only deals that were on it. Omit to keep the mark.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Changed5 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 / removals / items / properties / 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 / removals / items / properties / move_to / 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)$"
    • changedInput schema / properties / stages / items / properties / id / anyOf
      Previous value: -[
      -  {
      -    "format": "uuid",
      -    "pattern": "^([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)$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • 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)$"
  4. Changed1 schema field changed
    • changedInput schema / properties / stages / items / properties / signals / description
      Previous value: -"Events that move a deal here automatically: open: lead_created, human_joined, hot, invoiced, booked; won: paid, converted; lost: lost."New value: +"Events that move a deal here automatically: open: lead_created, human_joined, hot, reserve (client paused: «I'll think»), invoiced, booked; won: paid, converted; lost: lost."
  5. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, but the description carries most of the meaning: it says stages are replaced wholesale, that an omitted stage is deleted, that its deals must be relocated via removals, that only supplied fields change, and that the caller needs admin or owner role. Those details go well beyond the annotation hints and are exactly what an agent needs before a destructive update. It stops short of describing any response or error behavior for unreferenced deals.

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 replacement rule that the agent must not get wrong. The parenthetical constraints and ordering rule are compressed tightly, and no sentence repeats the schema or the 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 a destructive nested-array mutation with six parameters and no output schema, the description covers the risky parts: whole-list replacement, implicit deletion, deal relocation, partial-update semantics and permission requirements. What is missing is what happens when a removed stage has no entry in removals, and whether that is an error or a default; that is a real gap for a destructive tool, given the lack of response documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema description coverage is only 33%, the description supplies the meaning the schema cannot show on its own: the replacement semantics of stages, the 3-15 limit and ordering rule, and the purpose of removals as the destination preflight for orphaned deals. The remaining required ids, pipeline_id and workspace_id, are identified only by their field names, and those gaps keep it from a 5.

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 plus resource and names the three mutable fields: name, description and stages. It is clearly an update rather than a create or archive, but it never explicitly contrasts with dosai_create_pipeline or dosai_archive_pipeline, so sibling differentiation is implied rather than stated.

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?

It conveys critical usage syntax: pass the WHOLE stage list, keep existing stages by id, and declare removals. What it lacks is when-to-use routing: no mention of using create_pipeline to add a new pipeline or archive_pipeline to retire one, so the agent must infer the boundary from the names of those sibling tools.

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