Skip to main content
Glama

Save the owner's answer to a missing question

dosai_answer_bot_gap
Destructive

Save what the OWNER said about one question from dosai_list_bot_gaps: his answer in his own words, or a decision: human = the bot should hand such a question to a person, dismissed = not about this business, open = undo the decision. Never invent the answer yourself. Free; the bot does not change until dosai_write_bot_gaps. 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>",
      "question_id": "<question_id>"
    },
    "name": "dosai_answer_bot_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerNoThe owner's answer; empty string erases it.
decisionNo
project_idYesFrom dosai_list_projects.
question_idYes

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 / question_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 readOnlyHint=false and destructiveHint=true; the description adds the access requirement (admin or owner role), the cost profile ('Free'), and the crucial non-obvious fact that saving has no effect until dosai_write_bot_gaps runs. It also implies why the tool is destructive via 'empty string erases it' and 'open = undo the decision', which explains rather than contradicts the destructiveHint. It does not describe whether a previously saved answer is overwritten or versioned, which is the main residual gap.

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 what gets saved, then the enum decisions, then the safeguard, cost, and permission note — a sensible priority order. The middle clause ('his answer in his own words, or a decision: human = ..., dismissed = ..., open = ...') is dense and slightly run-on, but every element earns its place; nothing is padding.

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 4-parameter mutation tool with no output schema, the definition supplies the permission gate, cost, input source, upstream dependency, and downstream effect, which covers what an agent needs to call it correctly. What is missing is modest: the response shape on success and whether an existing answer is replaced rather than appended.

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?

With only 50% schema coverage, the description compensates well: it explains the meaning of all three decision values (human/dismissed/open) that the bare enum does not describe, and clarifies that the answer is the owner's own words with an erasure semantics for empty input. question_id has no schema description but is anchored by 'one question from dosai_list_bot_gaps'. project_id's provenance is left entirely to the schema.

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?

Specific verb ('Save') plus a precisely scoped resource ('what the OWNER said about one question from dosai_list_bot_gaps'), and it names the counterpart tool dosai_write_bot_gaps that actually changes bot behavior. An agent can distinguish this from the sibling write/apply tool without opening either 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?

Establishes the workflow context: the question comes from dosai_list_bot_gaps, this only records the owner's input, and nothing changes downstream until dosai_write_bot_gaps is called. It also states a hard constraint ('Never invent the answer yourself') that steers the agent away from fabricating content. No explicit when-not-to-use case (e.g., what to do if no owner answer exists yet), which keeps it short of a 5.

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