Skip to main content
Glama

create_table

Draws a table on a Miro board as grouped rectangle shapes, with an optional header row and editable cell IDs, since native tables are unsupported via the Web SDK.

Instructions

Draw a table as a grid of rectangle shapes, grouped. Native Miro tables cannot be created or read through the Web SDK (they show up as type "unsupported"; read one with capture). rows[0] is the header when header is true. x/y = top-left (board coordinates). cells are ids row by row; edit a cell with update_items.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rows": "<rows>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "create_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
rowsYes
headerNo
colWidthNo
parentIdNo
rowHeightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, closed-world), so the description's job is added context — and it delivers: the tool emits a group of rectangle items, and native tables are invisible to the SDK ('unsupported'). It stops short of saying what is returned (group id / cell ids) or how parentId affects placement.

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?

Four tight sentences, each adding a distinct fact (what it draws, the native-table caveat, header convention, coordinates, cell editing). Nothing repeats the schema or annotations, and the most important caveat is front-loaded.

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

Completeness3/5

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

For a 7-parameter mutation tool with no output schema, the definition covers the conceptual model well but omits return values (what identifiers come back) and the meaning of parentId and the sizing parameters. An agent could call it, but would guess on three inputs.

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 0%, so the description must carry the load. It explains rows[0]-as-header, x/y as top-left board coordinates, and row-by-row cell ordering, but leaves colWidth, rowHeight, and parentId entirely undefined in both schema and description.

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 outcome: 'Draw a table as a grid of rectangle shapes, grouped.' It also disambiguates the resource by explaining that this is NOT a native Miro table, which prevents the agent from assuming table semantics.

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?

Gives concrete routing for adjacent tasks: read a native table with 'capture', edit a cell with 'update_items'. It does not explicitly contrast with create_items for the general 'make shapes' case, but the alternatives it names carry clear conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.