google-workspace-mcp-advanced

get_messages

Retrieve messages from a Google Chat space with customizable page size and ordering. Returns formatted messages for easy reading.

Instructions

Retrieves messages from a Google Chat space.

Returns: str: Formatted messages from the specified space.

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": {
      "user_google_email": "<user_google_email>",
      "space_id": "<space_id>"
    },
    "name": "get_messages"
  }
}

Input Schema

Name	Required	Default
`user_google_email`	Yes
`space_id`	Yes
`page_size`	No
`order_by`	No	createTime desc

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.10Jun 2, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden but only says 'retrieves messages' and 'returns formatted messages'. It does not disclose ordering, pagination, authentication needs, or access constraints, leaving important behavioral aspects unspecified.

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?

The description is short, front-loaded, and free of fluff. Each sentence adds some information, though the overall content is thin.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no annotations, and sibling tools, the description is too minimal for reliable invocation. It lacks parameter explanations and behavioral context, making it incomplete even though an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 4 parameters with 0% schema description coverage, and the description does not explain any parameter semantics. It only mentions 'specified space' indirectly, omitting the meaning of user_google_email, order_by, and page_size.

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?

The description clearly states the tool retrieves messages from a Google Chat space, using a specific verb and resource. However, it doesn't explicitly differentiate from sibling tools like search_messages, so it falls short of a 5.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus search_messages or other alternatives. There is no mention of exclusions or preferred contexts.

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

Deploy Server