Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Move Wiki grid rows

wiki_grids_rows_move

Reorder a run of consecutive rows in a wiki grid by defining the starting row, destination, and optional row count; returns the updated revision.

Instructions

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

Returns the grid's new revision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes``row_id`` (first row to move) + destination (``position`` or ``after_row_id``) + optional ``rows_count`` + 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
    • 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 / properties / row_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / body / properties / row_id / default
      Removed value: -null
    • addedInput schema / properties / body / properties / row_id / type
      Added value: +"string"
    • changedInput schema / properties / body / required
      Previous value: -[
-  "revision"
-]New value: +[
+  "row_id"
+]
  2. First observedv0.67.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds that it returns the grid's new revision and that it operates on a run of rows, but it does not explain the optimistic-concurrency implication of the revision parameter or the failure behavior. With annotations carrying the safety load, a 3 is appropriate.

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 short sentences with zero waste and the core action front-loaded. Every clause 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 nested-object mutation tool with no output schema, the description supplies the key return value (the new revision) and the operation scope, while annotations and the rich schema cover safety and parameters. It stops short of explaining concurrency/failure semantics, so it is complete but not exhaustive.

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 row_id, position, revision, rows_count, and after_row_id fully, including the position/after_row_id alternative. The description adds no parameter-level meaning beyond what the schema provides, 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?

The description states a specific verb and resource ('Reorder rows inside a grid') and adds useful scope detail ('move a run of consecutive rows to a new position'). It is clearly distinguishable in intent from wiki_grids_columns_move, but it never explicitly routes against the many wiki_grids siblings (rows_create, rows_update, rows_delete).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The description never contrasts this with wiki_grids_rows_update/rows_create or the columns_move sibling, so an agent gets no help choosing among near-identical grid tools.

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