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, and tasks in chat rooms to document workflow progress without direct participant 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
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it's a creation/mutation operation (implied by 'Creates a new event'), the event types and their structured metadata requirements, and the return format ('JSON string containing the created event details'). However, it doesn't mention authentication needs, rate limits, or error handling beyond the error event type.

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?

The description is well-structured with clear sections (purpose, event types, sibling distinction, args, returns, examples) and front-loaded key information. However, the detailed event type explanations and multiple examples make it somewhat lengthy, though all content appears necessary for clarity.

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?

Given the tool's complexity (4 parameters with 0% schema coverage, no annotations, but with output schema), the description is remarkably complete. It explains all parameters semantically, documents the 5 event types with their metadata structures, distinguishes from siblings, provides usage guidelines, and includes comprehensive examples. The output schema existence means return values don't need explanation.

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?

Schema description coverage is 0%, so the description must compensate fully. It provides detailed semantic explanations for all 4 parameters: chat_id ('unique identifier of the chat room'), content ('Human-readable event content'), message_type (with all 5 enum values explained), and metadata ('Optional JSON object with structured event data. Structure varies by message_type'), including specific metadata structures for each event type.

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 clearly states the specific action ('Post an event in a chat room') and resource ('chat room'), with explicit differentiation from sibling tool 'create_agent_chat_message' for messages with mentions. The title 'null' is irrelevant as the description fully defines the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool ('Events do NOT require mentions - they report what happened rather than directing messages at participants') and when to use the alternative ('For text messages with mentions, use create_agent_chat_message instead'). This clearly distinguishes it from sibling tools.

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