yandex-wiki-search-mcp

Overview Schema Source Related Servers Discussions Admin

Update Wiki Grid Cells

grid_update_cells

Idempotent

Update specific cells in a Yandex Wiki dynamic table by providing row, column, and new value. Modify structured data directly, clearing a cell with null when needed.

Instructions

Update cells in a Yandex Wiki dynamic table. This changes structured data. Each cell patch must include row_id, value, and exactly one of column_id or column_slug.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cells`	Yes	Cell patches. Each object must include row_id, value, and exactly one of column_id or column_slug.
`grid_id`	Yes	Wiki dynamic table ID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cells`	No
`revision`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.0.1Aug 9, 2026

removedOutput schema / $defs

Removed value: -{
-  "WikiGridRow": {
-    "additionalProperties": true,
-    "properties": {
-      "color": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "title": "Color"
-      },
-      "id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "title": "Id"
-      },
-      "pinned": {
-        "anyOf": [
-          {
-            "type": "boolean"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "title": "Pinned"
-      },
-      "row": {
-        "items": {},
-        "title": "Row",
-        "type": "array"
-      }
-    },
-    "title": "WikiGridRow",
-    "type": "object"
-  }
-}

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"`POST /grids/{id}/cells` answers with `cells`, not `results`.\n\nIts own model rather than a shared one: `results` has a list default, so\nit is never dropped as empty, and a mutation reply carrying\n`\"results\": []` reads as \"nothing changed\" to an agent checking it."

addedOutput schema / properties / cells

Added value: +{
+  "anyOf": [
+    {
+      "items": {},
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedOutput schema / properties / results

Removed value: -{
-  "items": {
-    "$ref": "#/$defs/WikiGridRow"
-  },
-  "title": "Results",
-  "type": "array"
-}

removedOutput schema / properties / revision / title
```
Removed value: -"Revision"
```
removedOutput schema / title
```
Removed value: -"GridMutationResponse"
```

Addedv0.6.0Jul 26, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations provide idempotentHint=true but no readOnly/destructive hints. The description adds 'This changes structured data,' signaling mutation, which is useful. It does not, however, describe the effect on existing values (e.g., full replacement) or error behavior. This is acceptable given annotations cover idempotency, but still leaves gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, ~23 words. It front-loads the action and resource, then immediately states the critical constraint. No filler or redundancy. Every sentence earns its place.

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 that takes an array of cell patches, the description covers the essential purpose and constraint. An output schema exists, so return value explanation is handled. The only minor gap is not mentioning that cells is an array or that multiple patches are allowed, but the schema already defines this.

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 grid_id and cells. The description reiterates the 'exactly one of column_id or column_slug' constraint, which is also present in the schema. It adds no new meaning beyond schema, so baseline 3 is appropriate.

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 opens with 'Update cells in a Yandex Wiki dynamic table,' clearly stating the verb and resource. It distinguishes from sibling tools like grid_update (grid-level) and grid_add_rows (row-level) by specifying 'cells.' The phrase 'This changes structured data' reinforces the mutation scope.

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 clearly indicates when to use it (updating cells) and the required argument structure (row_id, value, exactly one of column_id/column_slug). However, it does not explicitly state exclusions or alternatives, such as using grid_add_rows for inserting rows or grid_update for changing grid settings, so it falls short of a perfect score.

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