Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

chat.users.sections.position

Reorder Google Chat sections by changing a section's relative position or sort order; supports dry runs and file-based request bodies.

Instructions

Changes the sort order of a section. For details, see Create and organize sections in Google Chat. Requires user authentication with the authorization scope: - https://www.googleapis.com/auth/chat.users.sections [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON PositionSectionRequest object accepting relativePosition, sortOrder; pass it via params or whole via body_file Siblings over the same resource: create, delete, list, patch.

Input Schema

NameRequiredDescriptionDefault
nameYes[URL path segment] Required. The resource name of the section to position. Format: `users/{user}/sections/{section}`
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 PositionSectionRequest object.
request_bodyNoRequest body of type PositionSectionRequest: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

NameRequiredDescriptionDefault
sectionNo

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 PositionSectionRequest object."
    • addedInput schema / properties / request_body
      Added value: +{
+  "description": "Request body of type PositionSectionRequest: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "relativePosition": {
+      "enum": [
+        "POSITION_UNSPECIFIED",
+        "START",
+        "END"
+      ],
+      "type": "string"
+    },
+    "sortOrder": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The resource name of the section to position. Format: `users/{user}/sections/{section}`"New value: +"[URL path segment] Required. The resource name of the section to position. Format: `users/{user}/sections/{section}`"
    • addedInput schema / properties / name / pattern
      Added value: +"^users/[^/]+/sections/[^/]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "section": {
+      "properties": {
+        "displayName": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "sortOrder": {
+          "type": "integer"
+        },
+        "type": {
+          "enum": [
+            "SECTION_TYPE_UNSPECIFIED",
+            "CUSTOM_SECTION",
+            "DEFAULT_DIRECT_MESSAGES",
+            "DEFAULT_SPACES",
+            "DEFAULT_APPS"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A3.7/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 burden and does well: it names the required OAuth scope, states the HTTP verb (POST), warns the call is refused under --readonly safety profiles, and says it returns the API's response resource as JSON. It stops short of stating whether the operation is idempotent or what happens if sortOrder and relativePosition conflict.

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 action is front-loaded in the first clause, then auth, transport, and body mechanics follow in a logical order. It is dense with links and scope URLs but each block (purpose, auth, HTTP behavior, body, siblings) earns its place; the doc link is the only soft filler.

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 and a 6-parameter schema including a nested body, the description covers auth requirements, mutation semantics, the readonly safeguard, and body mechanics, and an output schema exists so return values need not be spelled out. Only idempotency/error behavior is missing.

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 'name', 'dry_run', 'body_file', and the PositionSectionRequest fields, establishing a baseline of 3. The description reinforces the body shape (relativePosition, sortOrder) and the params-vs-body_file routing, adding marginal value but nothing the schema doesn't already state.

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 first sentence gives a precise verb and resource: 'Changes the sort order of a section,' which is clearly distinct from renaming (patch) or adding (create). It closes by enumerating the other operations on the resource (create, delete, list, patch), but doesn't explain how 'position' differs semantically from 'patch', so sibling differentiation is listed rather than argued.

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?

Usage is implied by the verb 'changes the sort order' and by the sibling roster, but there is no explicit statement of when to call this instead of chat.users.sections.patch or items.move. The authentication-scope and readonly-refusal notes are useful constraints but are behavioral, not selection guidance.

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