Skip to main content
Glama

set_native_table

Rewrite native table matrices, row heights, and column widths in RP files, cloning cells during expansion and optionally adding VectorShape merge overlays.

Instructions

改写原生 Table 矩阵/行高/列宽,扩容时克隆单元格,格支持 {runs} 多 run;可选用同页 VectorShape 模板生成视觉合并覆盖块。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node set-native-table.mjs input.rp output.rp table.json

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": {
      "args": "<args>"
    },
    "name": "set_native_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes
sessionNotrue 时 args 省略宿主源和输出,由当前链注入;多源工具仍传导入源。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-readonly, non-destructive, closed-world write, and the description goes further by explaining cell cloning during expansion, optional merge overlay generation, session-chain side effects, and an evidence restriction to verified samples. What is actually overwritten in the existing table is not spelled out, which keeps it short of a 5.

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

Conciseness3/5

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

The capability statement is front-loaded, but the remainder crams chain semantics, evidence rules and a CLI command line into one dense block, and the CLI invocation is operational trivia for a calling agent. Sentences earn partial keep, but the structure is not clean.

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 mutating, no-output-schema tool with two parameters, the description covers behavior, optional features, session mechanics and an applicability caveat. The remaining hole is the shape of args, which is the one required argument and is only hinted at by the CLI example.

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 50%. The description meaningfully expands the session parameter (injects host source and output from the current chain, multi-source tools still pass the import source). But the args array — the only required parameter — is never explained; its contents must be inferred from the trailing CLI line.

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 specifies a concrete verb and resource: rewriting native Table matrices, row heights and column widths, cloning cells on expansion, supporting multi-run {runs} cells, and optionally emitting visual merge overlay blocks from same-page VectorShape templates. No sibling tool in the list operates on tables, so the agent can identify it immediately.

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

Usage Guidelines3/5

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

It gives real invocation guidance: named calls omit host source/output and use the session chain, raw args use session:true with those two parameters omitted, and explicit paths do not advance the chain. It also limits applicability to gui-roundtrip verified samples per capabilities.md. However, no alternative tools or conditions for choosing them are named, so the guidance is conditional rather than comparative.

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