Табуля

files_resize

Idempotent

Sets column widths or row heights, in pixels. axis: 'columns' or 'rows'. size: pixel size (1-2000). indices: which to resize — column letters (e.g. ['A','C']) for columns, or row numbers (e.g. [1,5]) for rows. Omit indices to set the DEFAULT size for ALL columns/rows on the sheet. ('auto' fit-to-content is not available headless.) Requires edit permission. Signature: files_resize(file_uuid, axis, size, indices?, sheet?).

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>",
      "axis": "<axis>",
      "size": "<size>"
    },
    "name": "files_resize"
  }
}

Input Schema

Name	Required	Description
`axis`	Yes
`size`	Yes	Pixel size (1-2000).
`sheet`	No	Sheet name (defaults to the first sheet).
`indices`	No	Column letters for columns, or row numbers for rows. Omit to set the sheet default.
`file_uuid`	Yes

Output Schema

Name	Required	Description	Default
`file_uuid`	Yes
`sequence_number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare non-readOnly, idempotent, non-destructive. The description adds what the annotations don't: an edit-permission requirement, the headless limitation on auto-fit, and the side effect that omitting indices changes the DEFAULT size for all columns/rows. That default-size behaviour is a meaningful, non-obvious consequence.

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?

Short, front-loaded, and each clause carries information. The trailing signature line repeats the schema's required/optional shape and is mildly redundant, but it is compact and aids scanning.

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?

With an output schema present, the description need not explain returns, and it covers permissions, the size constraint, index formats, and default behaviour. It is complete enough to invoke correctly on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, and the description compensates well for the undocumented parts: it explains the axis enum, the size range of 1-2000, the exact index format (['A','C'] vs [1,5]), and the omit-means-default semantics for indices. Only 'sheet' is left to the schema.

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 opening sentence names a specific verb and resource ('Sets column widths or row heights, in pixels'), which clearly separates it from neighbours like files_format or files_borders that also alter sheet appearance. An agent can tell what this does without opening the 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?

It gives concrete selection guidance: omit indices to set the sheet-wide default, and 'auto' fit-to-content is unavailable headless. It does not explicitly compare itself with sibling formatting tools (files_format, files_borders), so the when-not guidance is only partially covered.

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?