Skip to main content
Glama
Google Chat MCP Server

Google Chat MCP Server

by hungvudang

Preview a message

preview
Read-only

Shows how a Google Chat message will appear before sending so you can check formatting and tone, then adjust it before posting.

Instructions

Show exactly how a message will look in Google Chat before sending it with send. Read google-chat://guide for tone and formatting.

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": "preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWhat to post, written for the people in the space.
formatNoHow the text is written: markdown (default), or chat if it already uses Google Chat markup. See google-chat://guide.markdown

Output Schema

NameRequiredDescriptionDefault
textYesThe text exactly as send would post it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a non-mutating render check. It adds the useful pointer to the google-chat://guide resource, but says nothing about whether the preview surfaces validation errors or how it differs from the final post beyond appearance.

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?

Two short sentences with the purpose front-loaded and the prerequisite resource noted second; nothing is redundant or padding.

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?

With an output schema present, return values needn't be explained, and the annotations cover the safety profile. The definition is complete for a simple two-parameter preview tool, though it could note whether the preview text is echoed back unchanged.

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 the text and format parameters are already documented, including the enum values and the default. The description adds no meaning beyond the schema and only indirectly gestures at format via the guide reference.

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 gives a specific verb plus resource (show how a message will look) and explicitly contrasts it with the sibling send, so an agent can distinguish preview from actually posting without opening the schema.

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?

It states the clear context of use ('before sending it with send') and points to the google-chat://guide resource for tone and formatting, but offers no explicit when-not-to-use condition or statement about which tool to use if the preview should be skipped.

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