Skip to main content
Glama

send_message

Send a private message to any Kwork user using their user ID or username. Automatically resolves username to ID and returns confirmation.

Instructions

Отправить личное сообщение пользователю Kwork по user_id или username.

Когда использовать: для отправки сообщения конкретному пользователю. Можно указать user_id или username — при username система автоматически определит user_id. Возвращает: подтверждение отправки или сообщение об ошибке. Связанные: get_dialog — прочитать переписку перед ответом, get_user_info — узнать user_id по username.

ВНИМАНИЕ: сообщение будет реально отправлено пользователю на Kwork.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
user_idNo
usernameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Warns that the message will be actually sent, implies side effects consistent with openWorldHint annotation. No contradictions.

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?

Concise, front-loaded with action, includes usage, related tools, and warning. No unnecessary text.

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 purpose, parameters, behavior, and related tools. Output schema exists, so return info is handled.

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

Parameters4/5

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

Despite 0% schema coverage, description explains the trade-off between user_id and username, and system behavior for username. Text parameter is implied but not elaborated.

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?

Clearly states the action: sending a personal message to a Kwork user by user_id or username. Distinct from sibling tools like delete_message and edit_message.

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?

Explicitly states when to use ('для отправки сообщения'), mentions related tools (get_dialog, get_user_info), and includes a warning about real-world impact.

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/simonether/kwork-mcp'

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