Skip to main content
Glama

Change the lead funnel statuses

dosai_set_lead_statuses
Destructive

Replace the project's lead statuses (the funnel, at most 15). Read them with dosai_get_lead_statuses first and pass the id of every status that stays: a status with an id and a new name is renamed together with its leads, a status left out is deleted (refused while leads still sit on it). creates_lead = reaching it creates a lead card; is_terminal = the dialog is finished; funnel_kind: progress, won (deal) or lost. Requires editor role.

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": {
      "project_id": "<project_id>",
      "statuses": "<statuses>"
    },
    "name": "dosai_set_lead_statuses"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusesYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed2 schema fields changed
    • removedInput schema / properties / project_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 / statuses / 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)$"
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes well beyond that by spelling out what is destroyed (statuses left out of the array), the cascade effect (renames propagate to leads), and the guard condition that blocks deletion. The editor-role requirement and the 15-status cap are additional operational context not present in the annotations.

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?

Front-loaded with the action and scope, then the read-first instruction, then the per-field semantics. It is dense and semicolon-chained, which makes the flag explanations slightly harder to scan, but no sentence is filler.

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

Completeness5/5

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

For a destructive, no-output-schema mutation tool this is complete: it covers prerequisites, deletion and rename semantics, refusal conditions, permission requirements, and the meaning of every nested field. Nothing an agent needs in order to call it safely is missing.

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

Parameters5/5

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

With only 50% schema description coverage, the description compensates by defining the id contract precisely: id plus new name means rename, omitted id means new status, and an id left out of the array means deletion. It also explains the three nested flags (creates_lead, is_terminal, funnel_kind) that the schema leaves as bare enums/booleans.

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 ('Replace the project's lead statuses') plus scope ('the funnel, at most 15'), and explicitly contrasts with the read sibling dosai_get_lead_statuses. An agent can distinguish it from every other set_* tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit prerequisite ('Read them with dosai_get_lead_statuses first'), the rule for what to pass, and the consequence of omission (deletion, refused while leads still sit on it). It also names the required permission level ('Requires editor role'), which is exactly the when-to-use gating an agent needs.

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