Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Wiki grid

wiki_grids_get
Read-onlyIdempotent

Retrieve a Yandex Wiki grid by UUID, including structure, rows, and revision. Narrow large tables with server-side filters, column/row selection, sorting, and extra fields.

Instructions

A single dynamic table (grid) by its UUID, with structure, rows and revision.

Grids are the modern dynamic tables attached to a page; find a grid's id with pages_grids_list. Use row_filter/only_cols/only_rows/sort to narrow large grids server-side, and fields=attributes,user_permissions for extra blocks. The returned revision is what any subsequent write must send back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoRow sort, e.g. ``slug,-slug2``.
fieldsNoExtra blocks to include (CSV), e.g. ``attributes,user_permissions``.
grid_idYesThe grid's permanent UUID4 id.
revisionNoLoad this past revision instead of the current one.
only_colsNoReturn only these column slugs (CSV).
only_rowsNoReturn only these row ids (CSV).
row_filterNoServer-side row filter, e.g. ``[slug] ~ wiki``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.122.1
    • addedInput schema / properties / revision
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Load this past revision instead of the current one."
+}
  2. First observedv0.67.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. The description adds real behavioral value beyond that: the server-side narrowing behavior and the critical contract that the returned revision must be sent back on subsequent writes. It does not cover pagination or response size limits, keeping it at 4.

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?

Three tight sentences, front-loaded with the core purpose, then discovery/alternatives, then behavioral contract. No filler and every sentence carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and annotations covering the safety profile, the description carries the needed extras well: it names return contents (structure, rows, revision) and the write-back revision contract. Nothing essential for correct invocation is missing.

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 goes further by grouping the filtering parameters and explaining their shared purpose (narrowing large grids server-side) plus the fields param for extra blocks, adding intent beyond the schema's per-param examples.

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 a specific verb and resource ('Get a single dynamic table (grid) by its UUID') and clarifies what a grid is ('modern dynamic tables attached to a page'), which distinguishes it from siblings like wiki_grids_create, wiki_grids_update, and wiki_pages_grids_list. An agent can tell this is the read-one 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 Guidelines4/5

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

Explicitly routes to the alternative for discovery ('find a grid's id with pages_grids_list') and explains when to reach for the narrowing parameters ('to narrow large grids server-side'). It gives clear context but doesn't state exclusions or when not to use it directly, so it stops short of a full 5.

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