Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

chat.users.spaces.spaceNotificationSetting.patch

Updates a user's Google Chat space notification setting, including mute and notification preferences, via PATCH with a required update mask.

Instructions

Updates the space notification setting. For an example, see Update the caller's space notification setting. Requires user authentication with the authorization scope: - https://www.googleapis.com/auth/chat.users.spacesettings [HTTP PATCH] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON SpaceNotificationSetting object accepting muteSetting, name, notificationSetting; pass it via params or whole via body_file Siblings over the same resource: get.

Input Schema

NameRequiredDescriptionDefault
nameYes[URL path segment] Identifier. The resource name of the space notification setting. Format: `users/{user}/spaces/{space}/spaceNotificationSetting`.
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 SpaceNotificationSetting object.
updateMaskNo[query parameter] Required. Supported field paths: - `notification_setting` - `mute_setting`
request_bodyNoRequest body of type SpaceNotificationSetting: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

NameRequiredDescriptionDefault
nameNo
muteSettingNo
notificationSettingNo

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 SpaceNotificationSetting object."
    • addedInput schema / properties / request_body
      Added value: +{
+  "description": "Request body of type SpaceNotificationSetting: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "muteSetting": {
+      "enum": [
+        "MUTE_SETTING_UNSPECIFIED",
+        "UNMUTED",
+        "MUTED"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "notificationSetting": {
+      "enum": [
+        "NOTIFICATION_SETTING_UNSPECIFIED",
+        "ALL",
+        "MAIN_CONVERSATIONS",
+        "FOR_YOU",
+        "OFF"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed5 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Identifier. The resource name of the space notification setting. Format: `users/{user}/spaces/{space}/spaceNotificationSetting`."New value: +"[URL path segment] Identifier. The resource name of the space notification setting. Format: `users/{user}/spaces/{space}/spaceNotificationSetting`."
    • addedInput schema / properties / name / pattern
      Added value: +"^users/[^/]+/spaces/[^/]+/spaceNotificationSetting$"
    • changedInput schema / properties / updateMask / description
      Previous value: -"Required. Supported field paths: - `notification_setting` - `mute_setting`"New value: +"[query parameter] Required. Supported field paths: - `notification_setting` - `mute_setting`"
    • addedInput schema / properties / updateMask / format
      Added value: +"google-fieldmask"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "muteSetting": {
+      "enum": [
+        "MUTE_SETTING_UNSPECIFIED",
+        "UNMUTED",
+        "MUTED"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "notificationSetting": {
+      "enum": [
+        "NOTIFICATION_SETTING_UNSPECIFIED",
+        "ALL",
+        "MAIN_CONVERSATIONS",
+        "FOR_YOU",
+        "OFF"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses HTTP PATCH semantics, required user authentication and authorization scope, refusal under readonly safety profiles, and JSON response behavior. It does not explicitly describe reversibility or partial-update semantics beyond PATCH, but the key operational and auth constraints are 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 description is front-loaded with the core purpose and then provides necessary auth, body, and sibling context. It is fairly dense with links and details, but each sentence contributes useful operational information.

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?

For a mutation tool with no annotations but rich schema and output schema support, the description covers the key missing context: authentication, scope, PATCH behavior, readonly refusal, and body format. It does not explain every schema detail, but the schema already handles those, making the description sufficiently 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 the input schema already documents all parameters thoroughly. The description reinforces that the body accepts `muteSetting`, `name`, and `notificationSetting` and can be passed via `params` or `body_file`, but it does not add substantial new parameter semantics beyond the schema.

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 and resource: it updates the space notification setting. It also explicitly identifies the sibling `get` over the same resource, so an agent can distinguish read versus update behavior without inspecting 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?

The description makes clear this is the update operation for a space notification setting and names the `get` sibling for the same resource. It does not spell out explicit when-not conditions, but the usage context is clear enough for an agent to choose between get and patch.

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