Skip to main content
Glama
Google Chat MCP Server

Google Chat MCP Server

by hungvudang

Send a report

report

Sends a structured message with a title, labelled details, and link buttons to a Google Chat space, so teams receive organized updates in one post.

Instructions

Send a structured report to a Google Chat space: a title, optional plain text, labelled details and link buttons. 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": {
      "title": "<title>"
    },
    "name": "report"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoA few plain sentences, without Markdown.
linksNoButtons that open related pages.
spaceNoWhich space to post in: default. Leave it out to use default.
titleYesWhat the report is about, in one line.
fieldsNoLabelled details, shown one per line.
subtitleNoShort context shown under the title.
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
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is carried by structured data. The description adds two things beyond that: the action posts into an external Google Chat space, and there is a mandatory prerequisite document (google-chat://guide) to read before calling. It stops short of saying what a failure or partial post looks like, but it is consistent with and additive to the annotations.

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 sentences, front-loaded with the action and the content model, with the prerequisite placed last where it will be seen before invocation. Nothing is redundant, though the second sentence is a bare instruction rather than a reason, so it is not maximally economical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 annotations cover the safety profile. What remains missing for a 7-parameter outbound-posting tool is routing against the 'send' and 'preview' siblings and any hint about posting constraints in the target space. Adequate, but not complete.

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 every parameter is already documented, including space defaulting and threadKey reuse semantics. The description reinforces the title/text/fields/links grouping but adds no syntax, limits or format rules beyond the schema, so it sits at the baseline.

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 structured report to a Google Chat space') and enumerates the payload shape: title, optional plain text, labelled details, link buttons. That is far more specific than a restatement of the name. It does not, however, distinguish this from the sibling 'send' tool, leaving the agent to guess which one posts a structured card versus a plain message.

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?

The only usage instruction is the prerequisite 'Read google-chat://guide first', which is a genuine pointer to required context. There is no statement of when to choose report over the 'send' or 'preview' siblings, and no exclusions. Usage is implied by the tool's shape rather than guided.

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