Skip to main content
Glama

Create a pipeline

dosai_create_pipeline

A new sales pipeline with standard stages (rename and change them with dosai_update_pipeline). Admin or owner of the CRM project.

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>",
      "name": "<name>"
    },
    "name": "dosai_create_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo
workspace_idYesCRM project (workspace) id, as returned by dosai_list_workspaces.

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. Changed1 schema field changed
    • 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds two genuinely useful facts beyond that – the pipeline is seeded with default stages, and the caller must be admin or owner – but says nothing about what happens on duplicate names, failure modes, or the returned object.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short with no filler, and the sibling pointer is parenthesized so it doesn't interrupt the main statement. The telegraphic fragment style ('A new sales pipeline...') costs a little readability, but nothing is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter creation tool with an output schema absent, the description is only partially sufficient: it covers permissions and default stage seeding but omits what the response contains and gives no meaning for two of three parameters. An agent could invoke it plausibly, but without full confidence in the parameter semantics.

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

Parameters2/5

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

Schema coverage is only 33%: workspace_id is documented in the schema, while 'name' and 'description' are bare strings with length limits only. The description does not compensate – it never explains that 'name' is the pipeline label or what 'description' is for, leaving the two undocumented parameters to guesswork.

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?

Names the resource ('a new sales pipeline') and states what will exist afterwards ('standard stages'), which lets an agent distinguish this from dosai_update_pipeline. The sentence is a fragment with no verb, so the create action is only inferred from the tool name rather than stated outright.

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 concrete context: 'Admin or owner of the CRM project' is a prerequisite, and it routes post-creation stage edits to dosai_update_pipeline. It does not compare against sibling creation tools or say when a pipeline is needed versus other paths, so it stops short of full 5-level 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