Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

chat.users.spaces.updateSpaceReadState

Updates a user's read state within a Google Chat space to mark messages as read or unread. Sets the last read time for a user and space via PATCH.

Instructions

Updates a user's read state within a space, used to identify read and unread messages. For an example, see Update a user's space read state. Requires user authentication with the authorization scope: - https://www.googleapis.com/auth/chat.users.readstate [HTTP PATCH] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON SpaceReadState object accepting lastReadTime, name; pass it via params or whole via body_file Siblings over the same resource: getSpaceReadState.

Input Schema

NameRequiredDescriptionDefault
nameYes[URL path segment] Resource name of the space read state. Format: `users/{user}/spaces/{space}/spaceReadState`
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON SpaceReadState object.
updateMaskNo[query parameter] Required. The field paths to update. Currently supported field paths: - `last_read_time` When the `last_read_time` is before the latest message create time, the
request_bodyNoRequest body of type SpaceReadState: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

NameRequiredDescriptionDefault
nameNo
lastReadTimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / body_file / description
      Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON SpaceReadState object."
    • addedInput schema / properties / request_body
      Added value: +{
+  "description": "Request body of type SpaceReadState: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "lastReadTime": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed5 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Resource name of the space read state. Format: `users/{user}/spaces/{space}/spaceReadState`"New value: +"[URL path segment] Resource name of the space read state. Format: `users/{user}/spaces/{space}/spaceReadState`"
    • addedInput schema / properties / name / pattern
      Added value: +"^users/[^/]+/spaces/[^/]+/spaceReadState$"
    • changedInput schema / properties / updateMask / description
      Previous value: -"Required. The field paths to update. Currently supported field paths: - `last_read_time` When the `last_read_time` is before the latest message create time, the"New value: +"[query parameter] Required. The field paths to update. Currently supported field paths: - `last_read_time` When the `last_read_time` is before the latest message create time, the"
    • addedInput schema / properties / updateMask / format
      Added value: +"google-fieldmask"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "lastReadTime": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the required user auth scope, states that it is an HTTP PATCH, notes refusal under --readonly safety profiles, and describes the returned resource. It does not cover rate limits or idempotency, but the key safety and auth context is present.

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 purpose is front-loaded and the description is information-dense rather than padded. It is somewhat run-on in the latter half, where HTTP method, return value, body handling, and sibling guidance are packed together, but every part remains useful.

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?

Given the rich schema, output schema, and zero annotations, the description supplies the missing behavioral context: authentication, scope, HTTP method, readonly refusal, body handling, and sibling relationship. An agent has enough information 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 the schema already documents all parameters. The description adds some body-routing context by noting that the SpaceReadState body accepts lastReadTime and name and can be passed via params or body_file, but that largely repeats schema descriptions.

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 states a specific verb and resource: it updates a user's read state within a space. It also clarifies the effect, identifying read and unread messages, and names the sibling getSpaceReadState, so the agent can distinguish this mutation from the read counterpart.

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?

The description gives clear context for use and identifies the sibling getSpaceReadState over the same resource. It does not explicitly say when to choose getSpaceReadState versus this update tool, but the update-versus-read distinction is strongly implied.

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