Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update Wiki grid cells

wiki_grids_cells_update
Idempotent

Update individual wiki grid cells by row ID and column slug; repeat calls set the same values and return changed cells plus the grid's new revision.

Instructions

Set the value of individual grid cells (addressed by row id + column slug).

Repeating the same call sets the same values (idempotent). Returns the updated cells plus the grid's new revision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes``cells`` (each: ``row_id`` + ``column_slug`` + ``value``) + the current ``revision``.
grid_idYesThe grid's permanent UUID4 id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.122.1
    • removedInput schema / properties / body / properties / cells / items / properties / value / default
      Removed value: -null
    • removedInput schema / properties / body / properties / cells / items / properties / value / title
      Removed value: -"Value"
    • changedInput schema / properties / body / properties / cells / items / required
      Previous value: -[
-  "row_id",
-  "column_slug"
-]New value: +[
+  "row_id",
+  "column_slug",
+  "value"
+]
    • addedInput schema / properties / body / properties / revision / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / body / properties / revision / default
      Added value: +null
    • changedInput schema / properties / body / properties / revision / description
      Previous value: -"Current grid revision (optimistic lock)."New value: +"Grid revision the edit is based on."
    • removedInput schema / properties / body / properties / revision / type
      Removed value: -"string"
    • changedInput schema / properties / body / required
      Previous value: -[
-  "revision",
-  "cells"
-]New value: +[
+  "cells"
+]
  2. First observedv0.67.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description's restatement of idempotency earns little. What it does add beyond structured data is the return payload (updated cells plus the grid's new revision), which matters because there is no output schema. It omits concurrency behavior around the revision field.

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 tight sentences with zero filler; the value/set operation is front-loaded and the idempotency/return note follows. Every clause contributes.

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?

With no output schema, the description usefully covers the return shape and confirms idempotency for a mutation tool. It does not explain what happens when the supplied revision is stale, which is the one behavioral detail an agent editing grid cells would likely need.

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, row_id, column_slug, value and revision. The description only restates the row id + column slug addressing and adds no format or constraint detail beyond that, so the baseline 3 applies.

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?

States a concrete verb+resource (set cell values) and specifies the addressing scheme (row id + column slug), which separates it from the coarse-grained wiki_grids_update and wiki_grids_rows_update siblings. It stops short of naming those alternatives, so an agent still has to open schemas to distinguish cell-level from row-level edits.

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 only implied by the word 'individual' — the caller is expected to infer this is for single-cell edits rather than wholesale grid updates. There is no explicit when-to-use vs wiki_grids_rows_update or wiki_grids_update, and no prerequisite or conflict 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