Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Move Wiki grid columns

wiki_grids_columns_move

Reorder columns in a Yandex Wiki grid by moving consecutive columns to a new position; returns the updated revision.

Instructions

Reorder columns inside a grid (move a run of consecutive columns to a new position).

Returns the grid's new revision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes``column_slug`` (first column to move) + ``position`` + optional ``columns_count`` + the current ``revision``.
grid_idYesThe grid's permanent UUID4 id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.122.1
    • removedInput schema / properties / body / properties / column_slug / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / body / properties / column_slug / default
      Removed value: -null
    • addedInput schema / properties / body / properties / column_slug / type
      Added value: +"string"
    • removedInput schema / properties / body / properties / position / anyOf
      Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / body / properties / position / default
      Removed value: -null
    • addedInput schema / properties / body / properties / position / type
      Added value: +"integer"
    • 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"
-]New value: +[
+  "column_slug",
+  "position"
+]
  2. First observedv0.67.0

TDQS

A3.8/5.0
Behavior3/5

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

The description states that it returns the grid's new revision, which is helpful context beyond the annotations. However, annotations already declare the key behavioral traits (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and the description does not add further behavioral details such as how column shifting affects existing positions, what happens on revision mismatch, or authentication requirements.

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, zero waste. The core action is front-loaded, and the return value note is concise and appropriately secondary. 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?

No output schema exists, so the description appropriately states the return value (new revision). The action and effect are clear, and parameters are fully covered by the schema. However, it does not address potential concurrency or revision-conflict behavior, which could matter for a non-idempotent move operation.

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 fully documents grid_id and the nested body parameters (column_slug, position, columns_count, revision). The description adds no additional parameter-level meaning beyond what the schema provides, which matches the baseline of 3 when the schema does the heavy lifting.

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 states a specific verb and resource: 'Reorder columns inside a grid' and clarifies it means 'move a run of consecutive columns to a new position'. This distinguishes the operation from sibling tools like wiki_grids_columns_create, wiki_grids_columns_delete, and wiki_grids_rows_move without needing to name them.

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 core action; there is no explicit when-to-use guidance, no mention of alternatives (e.g., wiki_grids_columns_update for property changes), and no when-not-to-use conditions. The action itself implies its use case, which is the minimum viable level.

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