Skip to main content
Glama

Throw away the price list draft

dosai_delete_price_draft
Destructive

Delete the uploaded draft of the price list with its file (list_id from dosai_get_price_list, the draft). The working price stays and the bot keeps calculating by it. Two steps. 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>",
      "list_id": "<list_id>"
    },
    "name": "dosai_delete_price_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYes
project_idYesFrom dosai_list_projects.
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. 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 / list_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 / 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)$"
  3. Added

TDQS

A4.5/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 adds what the annotations cannot: that the draft's file is also removed, that the working price survives and the bot keeps calculating on it, that confirmation is a two-step flow, and that editor role is required. This is exactly the extra context an agent needs before an irreversible action.

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-loads the destructive action and its scope in the first sentence, then adds the reassurance, the step count, and the permission requirement. The clipped phrasing ('Two steps. Requires editor role.') is efficient though slightly telegraphic.

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-parameter irreversible tool with no output schema, the description covers scope, side effects, prerequisites, and the confirmation requirement. It stops short of describing what the final call returns or whether the deleted file is recoverable, which are minor given the destructiveHint annotation.

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?

Schema coverage is 67%, with the only undocumented parameter being list_id; the description compensates by explaining it comes from dosai_get_price_list and refers to the draft specifically. The confirm_token procedure is documented in the schema, and the description reinforces the two-step nature, adding modest value on top.

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 ('Delete the uploaded draft of the price list with its file') and immediately disambiguates scope by saying the working price stays. It also points to dosai_get_price_list as the source of list_id, so an agent can distinguish draft deletion from other price-list operations without opening a 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 clear operating context: this removes the draft and its file only, the working price continues to be used for quoting, and the action needs two calls plus editor role. It does not name an alternative tool for removing the live price list, so an agent must infer that path, but the when-to-use condition for this tool is explicit.

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