Табуля

files_merge

Destructive

Merges a range of cells into one (keeping only the top-left value, clearing the rest), or splits merged cells back when unmerge=true. Use by_rows=true to merge each row of the range separately (one merged cell per row), and center=true to also center the merged content horizontally. Requires edit permission. Applied through the collaboration server. Signature: files_merge(file_uuid, range, sheet?, unmerge?, by_rows?, center?).

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": {
      "file_uuid": "<file_uuid>",
      "range": "<range>"
    },
    "name": "files_merge"
  }
}

Input Schema

Name	Required	Description
`range`	Yes	A1 range, e.g. 'A1:D1'.
`sheet`	No	Sheet name (defaults to the first sheet).
`center`	No	Also center the merged content horizontally (default false). Ignored when unmerge=true.
`by_rows`	No	Merge each row of the range separately into one cell per row, instead of the whole range into one (default false). Ignored when unmerge=true.
`unmerge`	No	Split merged cells overlapping the range instead of merging (default false).
`file_uuid`	Yes

Output Schema

Name	Required	Description	Default
`note`	No
`range`	Yes
`merged`	Yes
`file_uuid`	Yes
`sequence_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations declare destructiveHint=true, but the description adds the concrete consequence an agent actually needs: only the top-left value is kept and the rest is cleared. It also discloses the permission requirement and that changes go through the collaboration server, 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.

Conciseness4/5

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

The core behavior and destructive consequence are front-loaded in the first clause, and each subsequent clause covers a distinct flag. The trailing 'Signature: files_merge(...)' line duplicates the input schema and is the one piece of waste.

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 an output schema present there is no need to describe return values, and annotations cover the safety profile. The description fills the remaining gaps: data-loss semantics, permission requirement, and the interaction between unmerge and the other flags.

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 83%, so the schema already documents range, sheet, unmerge, by_rows and center, including the 'ignored when unmerge=true' interactions. The description restates those same semantics rather than adding new information, so this sits at the high-coverage 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 ('Merges a range of cells into one') and immediately covers the inverse operation ('splits merged cells back when unmerge=true'). No sibling tool in the list performs merging, and the description makes the merge/split duality unambiguous.

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 explains the mode switches: unmerge=true for the inverse operation, by_rows=true for per-row merging, center=true for alignment. It also states the edit-permission prerequisite. It stops short of naming when NOT to use it or pointing to an alternative, but no sibling offers overlapping functionality, so the guidance is effectively complete.

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

All Табуля tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?