Skip to main content
Glama

send_message

Send a TalkJS message in an active mentorship or intro-session conversation. Requires Authorization: Bearer. conversation_id comes from list_conversations. For an application that is not yet a mentorship, use send_application_message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "conversation_id": "<conversation_id>",
      "content": "<content>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
conversation_idYes

Output Schema

NameRequiredDescriptionDefault
kindNo
errorNo
statusNo
messageNo
next_stepNo
conversation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description is consistent with that write-but-non-destructive profile. It adds genuinely non-structured context: an Authorization: Bearer requirement and the provenance of conversation_id. It stops short of describing failure behavior (e.g. invalid or closed conversation) or delivery semantics.

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?

Three short sentences, front-loaded with the purpose, then prerequisites, then the sibling routing rule. No filler or repetition of the schema.

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?

An output schema exists, so return values need not be explained. Auth, parameter provenance, and sibling routing are all covered; only error handling and whether sending can create or open a conversation are left unspecified.

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 description coverage is 0% with two required parameters, so the description must carry the burden. It meaningfully explains where conversation_id comes from (list_conversations) but adds nothing about content beyond implying it is the message body — no format, length, or restriction detail.

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?

States a specific verb and resource (send a TalkJS message) plus the scope it applies to (active mentorship or intro-session conversations). It also names the sibling it is not, send_application_message, so an agent can distinguish the two without opening either schema.

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?

Gives both a positive condition (active mentorship or intro-session conversation) and an explicit alternative with the condition that selects it ('not yet a mentorship, use send_application_message'). It additionally tells the agent where to obtain the required conversation_id via list_conversations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources