Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Clone Wiki grid

wiki_grids_clone

Copy a grid onto another page asynchronously. Specify target page slug, optional title, and with_data to copy rows. Returns operation ID to poll for completion.

Instructions

Copy a grid onto another page (POST /grids/{id}/clone — asynchronous).

body.with_data=true copies the rows as well as the structure. Returns a deferred operation reference — poll operations_clone_inline_grid_get with the returned operation.id until it reaches a terminal status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesClone spec: ``target`` page slug (created if absent) + optional ``title`` and ``with_data`` (copy rows too).
grid_idYesThe grid's permanent UUID4 id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.122.1
    • addedInput schema / properties / body / properties / with_data / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / body / properties / with_data / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / body / properties / with_data / type
      Removed value: -"boolean"
  2. First observedv0.67.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly=false, idempotent=false, destructive=false). The description adds the crucial behavioral fact that the call is asynchronous and returns a deferred operation reference requiring polling of wiki_operations_clone_inline_grid_get, which annotations do not convey.

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 action, then the with_data nuance, then the async workflow. No filler.

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 an async mutation with a nested body and no output schema, the description supplies the two things an agent most needs: the async nature and the follow-up polling call. Only minor gaps remain, such as what target-page side effects to expect.

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 coverage is 100%, so the schema already documents grid_id, target, and title. The description restates the with_data semantics ('copies the rows as well as the structure') that the schema already provides, adding essentially no new parameter detail beyond baseline.

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 ('Copy a grid onto another page') plus the underlying endpoint. An agent can distinguish this from siblings like wiki_pages_clone and wiki_grids_create without opening any 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?

Clarifies the meaningful choice (with_data true copies rows vs structure only) and routes the agent to the correct polling tool. It lacks an explicit when-not-to-use statement or prerequisites, but the context is clear.

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