Skip to main content
Glama
logisky

logisheets-mcp

by logisky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_block

Create a structured table on a spreadsheet with typed columns, a read-only row key, and optional initial rows, enabling formula references via block names.

Instructions

Create a structured block (table) on a sheet. fields[0] is the row-key column (always read-only). Block ref name (name) is used as the first arg to BLOCKREF/BLOCKREFS in formulas.

Field types supported:

  • 'string' / 'number' — plain text/numeric cells.

  • 'boolean' — cell stores 0/1 or TRUE/FALSE; UI renders ✅/❌ if host has the widget set.

  • 'enum' (+ enum_id) — cell stores variant id; UI renders dropdown if host has the widget set. Watson auto-injects a variant-whitelist validation formula on the field so out-of-set writes light up as warnings even without widget rendering. Requires a prior define_enum_set call with matching id.

Rules (value_formula / validation / editability) are set separately via set_field_rule — this call only declares structure + initial rows. Auto-creates the target sheet if missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesBlock ref name. Used as the first arg to BLOCKREF/BLOCKREFS in formulas. Must be unique within the workbook.
sheetYesTarget sheet name.
fieldsYesColumn definitions in order. fields[0] is the row-key column.
positionYesTop-left cell of the block (0-indexed).
descriptionNoWhat this table is for, in a sentence or two: what a row represents, what the fields mean where the names are not obvious, and anything a later reader must not do to it (e.g. a field the craft maintains). Saved with the block and returned by describe_block, so write it for whoever opens the file next rather than for this conversation.
initial_rowsNoOptional initial rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / description
      Added value: +{
+  "description": "What this table is for, in a sentence or two: what a row represents, what the fields mean where the names are not obvious, and anything a later reader must not do to it (e.g. a field the craft maintains). Saved with the block and returned by describe_block, so write it for whoever opens the file next rather than for this conversation.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The description adds significant behavioral context beyond annotations: it notes that fields[0] is always read-only, that enum validation is auto-injected, and that the call auto-creates the target sheet. It does not contradict the annotations (readOnlyHint=false, destructiveHint=false) and appropriately discloses that it only declares structure and initial rows, not rules. This is valuable for the agent's understanding of side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with bullet points for field types and a separate note about rules. It front-loads the core purpose and keeps each sentence informative. While it is moderately long, it avoids fluff and each section serves a clear purpose, making it easy to scan.

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?

The description covers most important context: structure, field type semantics, dependencies, and auto-creation. However, it fails to mention date/datetime as supported field types, which is a notable gap given the schema's enum includes them. This omission could lead to incorrect tool usage. Other aspects like return values are not described, but since there is no output schema and the tool is a creation operation, that is acceptable.

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 parameters are well-documented. The description adds meaning for enum_id (requires prior define_enum_set) and the row-key column, which is helpful. However, it lists supported field types as only string/number, boolean, and enum, omitting date and datetime that are present in the schema's enum. This omission could mislead an agent into thinking those types are unsupported, reducing the added value.

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 clearly states the tool creates a structured block (table) on a sheet, specifies the row-key column behavior, and distinguishes itself from sibling tools like convert_to_block by emphasizing it creates a new block. The phrasing 'Create a structured block' is specific and action-oriented, leaving no ambiguity about the primary function.

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?

The description provides clear context on what this call does and does not do: it explicitly states that rules are set separately via set_field_rule, and it mentions auto-creating the sheet if missing. While it doesn't name alternative tools for different scenarios, it gives enough guidance on when to use this tool versus related ones by clarifying its scope (structure + initial rows only).

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