Skip to main content
Glama
Google Chat MCP Server

Google Chat MCP Server

by hungvudang

Send a message

send

Posts a text message to a Google Chat space, with optional thread replies to keep related updates together.

Instructions

Send a text message to a Google Chat space, optionally as a reply in a thread. Read google-chat://guide first.

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

Input Schema

NameRequiredDescriptionDefault
textYesWhat to post, written for the people in the space.
spaceNoWhich space to post in: default. Leave it out to use default.
formatNoHow the text is written: markdown (default), or chat if it already uses Google Chat markup. See google-chat://guide.markdown
threadKeyNoKeeps related posts in one thread. Reuse a key to reply, or pick a new one to start a thread.

Output Schema

NameRequiredDescriptionDefault
nameNoCreated message, spaces/<SPACE>/messages/<ID>.
threadNoThread of the message, spaces/<SPACE>/threads/<ID>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the key behavioral profile (not read-only, open-world, not idempotent, non-destructive), so the bar is lower. The description adds useful context that the guide must be consulted first and that thread replies are how related posts stay grouped, but it never warns that repeated invocations create duplicate messages despite idempotentHint=false, nor mentions rate limits or space membership requirements.

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?

Two short sentences with the action and the threading mode front-loaded and no wasted wording. The guide pointer is appended efficiently rather than padding, though it could be folded more tightly into the first sentence.

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?

An output schema exists so return values need not be explained, and the schema fully covers parameters. For a four-parameter send tool, the description plus annotations plus guide pointer give an agent everything needed to invoke it correctly.

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 100%, so all four parameters are already documented, including the space default and the format enum. The description's only added semantic is the optional threaded-reply framing, which merely echoes the schema's threadKey description; baseline 3 applies.

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 text message to a Google Chat space') plus the optional threading mode, which is enough to distinguish it from read-only siblings like preview and report. It does not explicitly contrast itself with those siblings (e.g., 'use preview to check formatting first'), so it stops short of full differentiation.

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

Usage Guidelines3/5

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

Provides a real prerequisite ('Read google-chat://guide first') and clarifies the optional reply-in-thread mode, which is genuine usage guidance. However, it never says when to prefer this over the sibling preview tool or what conditions make sending inappropriate, leaving the alternative routing to inference.

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

Deploy Server

Other Tools