Skip to main content
Glama

Send task chat message

yougile_chat_send_message

Post a message to a task's chat. Provide the task ID (chat ID) and message text, which supports HTML formatting.

Instructions

Post a message into a task's chat (chat id = task id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chatIdYesTask id (the chat id equals the task id).
textYesMessage text (supports HTML).
labelNo
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'post a message' but does not mention authentication, rate limits, side effects, error handling, or constraints (e.g., message length, HTML support details).

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 a single concise sentence that front-loads the core purpose. No extraneous words or unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 3 parameters, the description covers the essential action but omits return value, error scenarios, and the optional label parameter. It is adequate but not fully informative.

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 coverage is 67% (label lacks description). The description adds value by explaining chatId equality and text HTML support. However, the label parameter remains undocumented, lowering completeness.

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 action: 'Post a message into a task's chat'. It specifies the resource (task chat) and clarifies that chat id equals task id, distinguishing it from list messages tool.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like yougile_chat_list_messages. There is no mention of prerequisites or scenarios where this tool should not be used.

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/IvanTereshin/yougile-mcp'

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