Skip to main content
Glama
thenvoi

Thenvoi MCP Server

Official
by thenvoi

create_agent_chat_message

Send a text message in an agent chat room by mentioning recipients or providing their names. Resolves names automatically.

Instructions

Send a text message in a chat room.

Creates a new text message in a chat room. Messages MUST include at least
one @mention to ensure proper routing to recipients.

TWO WAYS TO SPECIFY RECIPIENTS:

Option 1 - Use `recipients` (recommended for LLMs):
    Provide comma-separated names. The tool resolves names to IDs automatically.
    Example: recipients="weather agent,sarah"

Option 2 - Use `mentions` (for libraries with caching):
    Provide a JSON array with pre-resolved IDs.
    Example: mentions='[{"id": "uuid-123", "name": "weather agent"}]'

If both are provided, `mentions` takes precedence (no API call needed).

For event-type messages (tool_call, tool_result, thought, error, etc.),
use create_agent_chat_event instead.

Args:
    chat_id: The unique identifier of the chat room (required).
    content: The message content/text (required).
    recipients: Comma-separated participant names to tag (LLM-friendly).
               Example: "weather agent,sarah,mike"
               Names are resolved to IDs via list_agent_chat_participants.
    mentions: JSON array of mentions with pre-resolved IDs (for libraries).
             Format: [{"id": "uuid", "name": "display_name"}, ...]
             When provided, skips name resolution (more efficient).

Returns:
    JSON string containing the created message details.

Examples:
    # LLM usage (names):
    create_agent_chat_message(chat_id="123", content="Hello!", recipients="weather agent")

    # Library usage (pre-resolved IDs):
    create_agent_chat_message(
        chat_id="123",
        content="Hello!",
        mentions='[{"id": "uuid-456", "name": "weather agent"}]'
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chat_idYes
contentYes
recipientsNo
mentionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the @mention requirement, recipient resolution behavior, and precedence rules. However, it does not mention error handling or permissions, though these are minor omissions for a create operation.

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 sections and examples, but slightly lengthy. Every sentence adds value, but could be tighter. Front-loaded with core purpose.

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?

Covers all aspects: purpose, parameters, usage guidelines, return value (JSON string). Sibling tool create_agent_chat_event is mentioned for event messages. Complete for an agent to select and invoke correctly.

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%, but description adds extensive meaning: explains chat_id, content, recipients (comma-separated names), mentions (JSON array), precedence rules, and examples. This fully compensates for the lack of schema descriptions.

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 tool sends a text message in a chat room and differentiates it from create_agent_chat_event for event-type messages. The verb 'send' and resource 'text message' are explicit.

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?

Provides explicit guidelines: must include at least one @mention, two ways to specify recipients (LLM-friendly vs. pre-resolved), and when to use each. Also directs to an alternative tool for event-type messages.

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