Skip to main content
Glama
Convocore MCP Server

Convocore MCP Server

by Moe03

add_conversation_note

Adds a note to a conversation's notes timeline so workspace teams and clients can see context in the dashboard; logged with author, IP, and time.

Instructions

Add a note to a conversation's notes timeline (visible to the workspace team and clients in the dashboard). Recorded in the workspace Logs with who, IP and time. Max 5000 characters. Prefer this over update_conversation, which cannot change notes.

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": {
      "agentId": "<agentId>",
      "convoId": "<convoId>",
      "text": "<text>"
    },
    "name": "add_conversation_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe note text (max 5000 characters).
agentIdYesThe agent ID
convoIdYesThe conversation ID
authorNameNoLabel for who is acting, e.g. "Claude via MCP". Only used because API-key calls have no signed-in person; it is shown on the note and in the audit log.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.6.17

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses that notes are client-visible in the dashboard, that the action is recorded in workspace Logs with who/IP/time, and the 5000-character cap. That audit-trail and visibility detail is the kind of side-effect context annotations cannot convey. It does not say what the call returns or whether repeated identical calls create duplicates (annotations already flag idempotentHint=false).

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 short sentences, front-loaded with the action, then side effects, then the alternative — no filler. The character limit is the only near-redundant clause, and it functions as a guardrail reminder.

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 single-purpose mutation with no output schema and 100% schema coverage, the definition supplies the crucial missing pieces: visibility, audit logging, and size limit. Only the return value/shape and permission requirements are left implicit.

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 100% and every parameter, including the nontrivial authorName explanation, is documented in the schema itself. The description only restates the 5000-character limit already present in the text property, adding no new semantics. Baseline 3 applies.

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?

States a specific verb and resource — 'Add a note to a conversation's notes timeline' — and immediately scopes the audience (workspace team and clients). An agent can distinguish it from list_conversation_notes, update_conversation_note, and delete_conversation_note 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?

Explicitly routes away from update_conversation with the reason ('cannot change notes'), which is exactly the comparative guidance an agent needs. It stops short of distinguishing this add path from update_conversation_note (creating a new note vs. editing an existing one), leaving one inference for the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools