Skip to main content
Glama
thenvoi

Thenvoi MCP Server

Official
by thenvoi

create_agent_chat_event

Post agent execution events like tool calls, results, thoughts, errors, or task updates to a chat room, enabling event tracking without user mentions.

Instructions

Post an event in a chat room (tool_call, tool_result, thought, error, task).

Creates a new event in a chat room. Events do NOT require mentions - they
report what happened rather than directing messages at participants.

Event types and their content/metadata structure:

- **tool_call**: Agent invokes a tool
  - content: Human-readable description (e.g., "Calling send_direct_message_service")
  - metadata: {"function": {"name": "fn_name", "arguments": {...}}, "id": "call_id", "type": "function"}

- **tool_result**: Result from tool execution
  - content: Human-readable summary (e.g., "Message sent successfully")
  - metadata: {"success": true, "message": "...", ...result data}

- **thought**: Agent's internal reasoning
  - content: The reasoning text
  - metadata: Optional

- **error**: Error or failure notification
  - content: Error message
  - metadata: {"error_code": "...", "details": {...}}

- **task**: Task-related message
  - content: Task message
  - metadata: Optional

For text messages with mentions, use create_agent_chat_message instead.

Args:
    chat_id: The unique identifier of the chat room (required).
    content: Human-readable event content (required).
    message_type: Event type (required). One of: 'tool_call', 'tool_result',
                'thought', 'error', 'task'.
    metadata: Optional JSON object with structured event data. Structure varies by message_type.

Returns:
    JSON string containing the created event details.

Examples:
    # Tool call event
    create_agent_chat_event(
        chat_id="123",
        content="Calling weather_service",
        message_type="tool_call",
        metadata='{"function": {"name": "get_weather", "arguments": {"city": "NYC"}}, "id": "call_1", "type": "function"}'
    )

    # Tool result event
    create_agent_chat_event(
        chat_id="123",
        content="Weather retrieved successfully",
        message_type="tool_result",
        metadata='{"success": true, "temperature": 72, "conditions": "sunny"}'
    )

    # Thought event
    create_agent_chat_event(
        chat_id="123",
        content="I should check the weather before suggesting outdoor activities",
        message_type="thought"
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chat_idYes
contentYes
message_typeYes
metadataNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description bears full burden. It explains events don't require mentions and describes event type structures. But it does not disclose whether events persist, visibility, required permissions, or side effects.

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

Conciseness4/5

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

Well-structured with headers, bullet lists, and examples. Slightly verbose but every section adds value. Could trim redundant 'human-readable' phrases.

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?

Covers purpose, parameter semantics, event types, sibling differentiation, and provides examples. Missing behavioral context like persistence and permissions, but otherwise complete for a 4-parameter tool with output schema.

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

Parameters5/5

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

Adds significant detail beyond the schema: chat_id as unique identifier, content as human-readable, message_type as enum with allowed values explained via examples, metadata as optional JSON with structure by type. The 0% schema coverage makes this critical and it delivers.

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?

Description clearly states it posts events in a chat room, lists five specific event types, and explicitly differentiates from create_agent_chat_message for text messages with mentions. Uses a specific verb 'post' and resource 'event'.

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 says to use create_agent_chat_message for text messages with mentions, and notes events don't require mentions. However, it doesn't detail when to use each event type or contrast with other tools like send_my_chat_message.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thenvoi/thenvoi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server