Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update Wiki grid

wiki_grids_update
Idempotent

Rename or re-sort a grid by sending its current revision to prevent write errors. Returns the new revision.

Instructions

Rename or re-sort a grid (POST-not-PATCH quirk handled by the SDK).

body.revision must match the grid's current revision (read it off grids_get); a mismatch fails the write. Returns the grid's new revision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesEditable fields (``title``, ``default_sort``) plus the required ``revision``.
grid_idYesThe grid's permanent UUID4 id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.122.1
    • changedInput schema / properties / body / description
      Previous value: -"Editable fields (``title``, ``default_sort``) plus the required ``revision`` (optimistic lock)."New value: +"Editable fields (``title``, ``default_sort``) plus the required ``revision``."
    • 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"
    • removedInput schema / properties / body / required
      Removed value: -[
-  "revision"
-]
  2. First observedv0.67.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive). The description adds real context beyond them: the POST-not-PATCH quirk, the optimistic-concurrency rule that a stale revision fails the write, and that it returns the new revision. This failure-mode disclosure is exactly the kind of behavioral detail annotations cannot convey.

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?

Three tight sentences with the operation front-loaded, followed by the revision constraint and return value. The parenthetical about the SDK handling the POST-not-PATCH quirk is a slight aside but still informative rather than wasteful.

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 nested-body mutation with no output schema, the description covers the essentials: what it edits, the revision precondition, and the returned revision. Annotations carry the safety profile and the schema fully documents the nested fields, leaving no critical gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description rises above it by clarifying the otherwise-vague 'revision' parameter: it must equal the grid's current revision and a mismatch fails the write, adding a concrete constraint the schema field text does not.

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?

States specific verbs and resource ('Rename or re-sort a grid'), which cleanly separates it from sibling grid tools like wiki_grids_columns_update, wiki_grids_rows_update, and wiki_grids_cells_update. An agent can identify the operation without opening 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides a prerequisite workflow step (read the current revision off grids_get before writing), which is genuinely useful. However it does not state when to choose this over alternatives such as cloning or column updates, and gives no explicit exclusions.

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