Convocore

add_conversation_note

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

Name	Required	Description
`text`	Yes	The note text (max 5000 characters).
`agentId`	Yes	The agent ID
`convoId`	Yes	The conversation ID
`authorName`	No	Label 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.

First observedOct 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: audience disclosure (workspace team and clients see the note in the dashboard), audit logging with who/IP/time, and a 5000-character limit. Annotations already establish this is a non-destructive write; the description adds visibility and accountability consequences.

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 tight sentences: purpose first, then behavioral consequences, then the routing hint. Every clause carries information an agent needs; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-param, non-destructive append tool with full schema coverage and no output schema, everything needed is present: effect, visibility, audit trail, size limit, and sibling preference.

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%, so all four parameters including authorName are documented in the schema itself. The description only restates the 5000-character cap for text, adding nothing new about parameter meaning — 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+resource ("Add a note to a conversation's notes timeline") and immediately clarifies the effect (visible in dashboard to team and clients). An agent can distinguish it from update_conversation 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?

Explicitly routes the agent away from update_conversation ("which cannot change notes"), giving an alternative plus the reason. It does not mention the related update_conversation_note or delete_conversation_note siblings, so guidance is clear but not exhaustive.

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

All Convocore tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?