Skip to main content
Glama

Project name, company facts, pause

dosai_update_project
Destructive

Change the project's name, the business name, industry, the "company info" text (facts the bot reads with every answer: address, hours, contacts, conditions; keep it short, long texts belong in the knowledge base), or pause and resume the bot for everyone (status paused = the bot answers nobody). Only the fields you pass change. Requires admin or owner 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>"
    },
    "name": "dosai_update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
statusNo
industryNo
project_idYesFrom dosai_list_projects.
company_infoNoReplaces the whole company info text.
company_nameNo

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. Changed1 schema field 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)$"
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds real context on top: partial-update semantics ("Only the fields you pass change"), the blast radius of pausing ("the bot answers nobody"), and the role requirement. It stops short of saying whether resume restores prior behavior or how in-flight conversations are affected.

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?

A single dense sentence, but it is front-loaded with the mutable fields and the parentheticals each carry non-obvious information rather than filler. Slightly heavy nesting, yet nothing is wasted.

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, no-output-schema mutation with 6 parameters, the description covers the essentials: partial-update behavior, permission requirement, and the consequence of the paused state. Minor gaps remain around reversibility of pause and whether company_info replacement is recoverable.

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 only 33%, so the description must compensate, and it does: it explains what company_info actually is ("facts the bot reads with every answer: address, hours, contacts, conditions") and what status=paused means operationally. Only project_id is left to the schema, which already documents it as coming from dosai_list_projects.

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 a specific verb ("Change") and enumerates exactly which project fields are mutable: name, business name, industry, company info text, and pause/resume status. That field list lets an agent separate this from siblings like dosai_update_bot_settings or dosai_update_booking_settings 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 Guidelines4/5

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

It gives a clear routing rule for content placement ("keep it short, long texts belong in the knowledge base") and states the prerequisite "Requires admin or owner role." It does not explicitly say when to prefer this over other update tools, but the field enumeration makes the boundary obvious.

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