Skip to main content
Glama

send_message_to_client

Send a chat message to one of the coach's clients (confirm-gated). It lands in the client's chat and sends them a push notification, exactly as if the coach typed it. Use the client's User._id (from list_clients). Write in the coach's voice, first person.

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": {
      "clientId": "<clientId>",
      "text": "<text>"
    },
    "name": "send_message_to_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds genuinely useful behavior beyond that: the message lands in the client's chat, triggers a push notification, and appears exactly as if the coach typed it. What it omits is the irreversibility of the side effect (a sent message cannot be recalled) and what the preview response contains, which matter for a real-person-facing write.

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 what the tool does, then delivery effect, then ID source and voice. No redundant phrasing or filler; every clause carries information.

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?

For a simple 3-parameter tool with no output schema, the description covers purpose, ID provenance, confirm gating, and delivery side effects, which is close to sufficient. Remaining gaps are edge behavior — failure modes if clientId is invalid, and what the preview returns — which are minor for this complexity.

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 only 33% (only 'confirm' is documented), so the description must compensate. It does partially: clientId is pinned to a User._id sourced from list_clients, and 'text' gets voice guidance ('coach's voice, first person'). However, nothing is said about text length limits, formatting, or whether confirm behavior applies per-call, leaving gaps on two of three parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 chat message to one of the coach's clients') and scopes it to a single client's chat, which implicitly separates it from broadcast siblings like send_organization_announcement or message_groups. It stops short of naming an alternative explicitly, so an agent must infer the 1:1 boundary from 'one of' and 'the client's chat.'

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

Usage Guidelines4/5

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

Gives actionable context: use the client's User._id obtained from list_clients, and write in the coach's first-person voice. The confirm gate is flagged ('confirm-gated'), but there are no explicit exclusions telling the agent when not to use this versus bulk or group messaging.

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.