Convocore

update_conversation_note

Idempotent

Replace the text of one existing note. The previous text is kept in the workspace Logs with who edited it, from which IP and when.

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>",
      "noteId": "<noteId>",
      "text": "<text>"
    },
    "name": "update_conversation_note"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The new note text (max 5000 characters).
`noteId`	Yes	The note id from list_conversation_notes.
`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.2/5.0

Behavior4/5

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

Annotations already declare the tool is not read-only, is idempotent, and is non-destructive. The description adds valuable behavioral context beyond that: the previous text is retained in workspace Logs along with editor identity, IP, and timestamp, which is important for an edit operation.

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?

The description is two sentences with no wasted words. The core action is front-loaded, followed by the audit-retention detail that materially affects how an agent should understand the operation.

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 mutation tool with full schema coverage and annotations covering safety traits, the description is nearly complete: it explains replacement behavior and audit logging. It does not discuss permissions or error conditions, but those are less critical here and the key behavioral nuance is present.

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 description coverage is 100%, so all five parameters are already documented in the schema. The description reinforces that the note is existing and that text is replaced, but does not add syntax or usage details beyond what the schema provides, so the 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?

The description states a specific verb and resource: 'Replace the text of one existing note.' It clearly scopes the operation to an existing note, distinguishing it from add_conversation_note and delete_conversation_note without needing to name them explicitly.

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?

The phrase 'one existing note' implies this is for editing, not creating or deleting. It gives clear context for when to use it, but does not explicitly state when not to use it or name alternatives such as add_conversation_note.

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?