Skip to main content
Glama

Switch the price list on, confirm an item, re-read the sheet

dosai_manage_price_list
Destructive

One action on the price list (ids from dosai_get_price_list). activate: make the draft the working price (refused while an item's grid is unconfirmed or has no prices). confirm_item: the owner confirms an item's grid was read correctly; swap=true first swaps its rows and columns. set_bot_enabled: whether the bot calculates prices by this list. sync_sheet: re-read the Google Sheet now. Throwing a draft away: dosai_delete_price_draft. 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>",
      "action": "<action>"
    },
    "name": "dosai_manage_price_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
swapNo
actionYes
enabledNoFor set_bot_enabled.
item_idNoFor confirm_item.
list_idNoFor activate and set_bot_enabled.
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. Changed3 schema fields changed
    • removedInput schema / properties / item_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 / 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
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds real context beyond that: the preconditions that block activate, the permission requirement, and the fact that sync_sheet re-reads the external sheet now. It stops short of saying what set_bot_enabled does to existing calculated prices or whether confirmation is revocable.

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?

Action semantics are front-loaded and each clause earns its place, with no filler or restatement of the title. The telegraphic style is efficient but occasionally clipped, so an agent must parse colon-separated fragments rather than full sentences.

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 six-parameter mutation tool with no output schema and destructive annotations, the description covers action selection, preconditions, permissions, and the excluded deletion path. It does not say what a successful sync_sheet or set_bot_enabled returns or whether either is reversible, which is a modest gap rather than a blocking one.

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%, and the description compensates for the gaps: swap is only defined here ('swap=true first swaps its rows and columns'), and enabled/item_id/list_id are tied to their actions (set_bot_enabled, confirm_item, activate/set_bot_enabled). project_id relies on the schema's own 'From dosai_list_projects' note, which is adequate.

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?

The description names the resource (price list) and enumerates all four actions with a one-clause definition of each: activate, confirm_item, set_bot_enabled, sync_sheet. It also points to dosai_get_price_list for the ids and to dosai_delete_price_draft for the case it does not cover, so an agent can distinguish it from siblings without opening any 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?

It gives per-action conditions: activate is 'refused while an item's grid is unconfirmed or has no prices', confirm_item is the owner's confirmation step, swap=true must precede it, and discarding a draft is explicitly routed elsewhere. It also states the editor-role prerequisite, leaving little to inference.

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