MCP 2025-06-18

log_event

Attach a note, finding, evidence, or handoff to an agent session.

Input schema

This schema is shared with tools/list. The server also verifies current scopes and resource-level access before returning data or changing a record.

Synthetic example · JSON

{
  "type": "object",
  "properties": {
    "sessionId": {
      "type": "string",
      "description": "Session ID"
    },
    "kind": {
      "enum": [
        "note",
        "finding",
        "evidence",
        "handoff",
        "status",
        "heartbeat"
      ]
    },
    "message": {
      "type": "string",
      "description": "Event content"
    },
    "metadata": {
      "type": "object"
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Unique retry key"
    }
  },
  "required": [
    "sessionId",
    "message",
    "idempotencyKey"
  ],
  "additionalProperties": false
}

Call this tool

Use the tool name below in params.name. Supply the exact arguments described above; this envelope deliberately leaves required resource values for your authorized context.

Synthetic example · JSON

{
  "jsonrpc": "2.0",
  "id": "example_request",
  "method": "tools/call",
  "params": {
    "name": "log_event",
    "arguments": {}
  }
}

Read the result before continuing

Inspect protocol errors and the tool result’s isError flag. A request being accepted is not proof of an external action completing. Preserve correlation IDs and unchanged mutation idempotency keys across safe retries.