Skip to main content
Glama

Write the owner's answers into the bot

dosai_write_bot_gaps
Destructive

Put the saved answers into the bot (its description, company info or knowledge base, the platform chooses where). Three actions. propose: returns what exactly will change, line by line, and a write_id; show it to the owner. apply: write it, with the write_id, after the owner's yes. undo: put everything back by write_id. Free for the owner. 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>",
      "action": "<action>"
    },
    "name": "dosai_write_bot_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
languageNoLanguage of the inserted headings. Default ru.
write_idNoFor apply and undo: the id returned by propose.
project_idYesFrom dosai_list_projects.
question_idsNoFor propose: only these questions; omit for all answered ones.

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 / 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 / question_ids / items / 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 / write_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.2/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it discloses that propose returns a preview plus a write_id, that apply is gated on owner consent, that undo restores prior state, that an admin or owner role is required, and that the operation is free for the owner. It also flags that the platform chooses the destination, which is real nondeterminism the agent otherwise could not anticipate.

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 core action, then a compact 'Three actions' list that maps one clause to each enum value, plus role and cost notes at the end. The telegraphic, clipped phrasing ('apply: write it') is efficient but occasionally terse enough to read as shorthand.

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, multi-mode write tool with no output schema, the description covers the full action lifecycle, consent gating, reversibility, and authorization. It leaves out what apply/undo actually return and any expiry or idempotency limits on write_id, which an agent executing a destructive call would want.

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 80%, so structured fields already carry most parameter meaning. The description still adds value by explaining that write_id comes from propose and is used by apply and undo, which conveys the required call sequence rather than just the field type.

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?

Opens with a specific verb plus resource ('Put the saved answers into the bot') and names the possible destinations (description, company info, knowledge base), which separates it from dosai_answer_bot_gap (saving an answer) and dosai_compose_bot_description. It stops short of naming a sibling tool explicitly, so discrimination relies on the reader knowing the catalog.

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 per-action guidance that amounts to a workflow: propose to preview line by line and show the owner, apply only after the owner's yes, undo to revert. That is clear when-to-use guidance for all three modes. It does not name an alternative tool or state when not to use this one at all.

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