Skip to main content
Glama

Add a note to a dialog

dosai_add_conversation_note

Leave an internal note on a dialog for the team. The client does not see it. 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>",
      "conversation_id": "<conversation_id>",
      "text": "<text>"
    },
    "name": "dosai_add_conversation_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
project_idYesFrom dosai_list_projects.
conversation_idYesFrom dosai_list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / conversation_id / description
      Previous value: -"Conversation id, as returned by dosai_list_conversations."New value: +"From dosai_list_conversations."
  2. 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."
  3. Changed2 schema fields changed
    • removedInput schema / properties / conversation_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)$"
  4. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the description earns credit for what it adds: the note is invisible to the client and an editor role is required. It does not cover whether notes are append-only/immutable once posted or how the note is echoed back on success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three very short sentences, front-loaded with the action, then the visibility consequence, then the permission gate. No filler or redundant restatement of the name.

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 simple three-required-parameter mutation with no output schema and no nested objects, the description covers purpose, visibility, and authorization. A brief note on whether the note is editable/deletable after creation or on formatting expectations would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%: project_id and conversation_id already say where their UUIDs come from, and text carries min/max length constraints in the schema. The description adds nothing about the text payload (plain vs. markdown, 4000-char limit, any disallowed content), so it only reaches the baseline for a mostly-documented schema.

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?

"Leave an internal note on a dialog" names a specific verb (leave/add) and resource (note on a dialog) and adds the scoping property "internal" that separates it from a client-facing message. It does not explicitly distinguish itself from the similarly named sibling dosai_add_contact_note, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The "for the team / the client does not see it" framing implies when to use it (internal-only annotations), and the editor-role requirement hints at an access precondition. However, there is no explicit when-not-to-use guidance and no named alternative such as dosai_add_contact_note or dosai_list_conversation_notes for verification.

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