Табуля

files_update_chart

Updates an existing native chart by id. Only the provided (non-null) fields change; everything else is preserved. To MOVE the chart set position; to RESIZE set width_cells/height_cells. Set chart_name to rename (display name, not the title); set title to '' to remove the title. series_columns replaces the plotted series (0-based column indexes within the data range, category column excluded). Requires edit permission. Signature: files_update_chart(file_uuid, chart_id, sheet?, chart_type?, data_range?, chart_name?, title?, position?, width_cells?, height_cells?, transpose?, first_row_headers?, first_col_labels?, x_column?, series_columns?).

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>",
      "chart_id": "<chart_id>"
    },
    "name": "files_update_chart"
  }
}

Input Schema

Name	Required	Description
`sheet`	No	Sheet name (defaults to the first sheet).
`title`	No	New title; '' removes it. Null keeps current.
`chart_id`	Yes	Id of the chart to update (from files_add_chart or the sheet context).
`position`	No	New top-left anchor cell (A1). Null keeps current.
`x_column`	No	0-based category column index. Null keeps current.
`file_uuid`	Yes
`transpose`	No
`chart_name`	No	New display name. Null keeps current.
`chart_type`	No	New chart type. Null keeps current.
`data_range`	No	New A1 data range. Null keeps current.
`width_cells`	No	New width in columns (min 2). Null keeps current.
`height_cells`	No	New height in rows (min 4). Null keeps current.
`series_columns`	No	0-based series column indexes to plot. Null keeps current.
`first_col_labels`	No
`first_row_headers`	No

Output Schema

Name	Required	Description	Default
`chart_id`	Yes
`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 cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds real context beyond them: null fields are preserved, title='' removes rather than blanks the title, and edit permission is required. It stops short of describing failure modes (bad chart_id, invalid range) or whether re-applying the same payload is safe, which matters given idempotentHint=false.

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?

Front-loaded and dense: purpose, preservation rule, per-goal parameter routing, and permission all land in three sentences. The trailing redundant 'Signature:' line restating all 15 parameter names adds no information over the schema and should be cut.

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 15-parameter mutation tool with an output schema and useful annotations, this is largely complete: it specifies update semantics, permission, and how the tricky fields interact. Minor gaps remain on the three boolean flags and on what happens when the target chart or range is invalid.

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?

Above the 73%-coverage baseline, the description disambiguates the two lookalike fields (chart_name = display name, title = chart title) and clarifies series_columns as 0-based indexes within the data range with the category column excluded. It leaves transpose, first_row_headers, and first_col_labels undiscussed in both description and schema descriptions.

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 ("Updates an existing native chart by id"), which immediately separates it from files_add_chart and files_delete_chart. The partial-update scoping ("Only the provided (non-null) fields change") tells the agent precisely what kind of update this is.

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 clear operational routing inside the tool: position for MOVE, width_cells/height_cells for RESIZE, chart_name vs title for naming/removal, series_columns for re-plotting. It does not explicitly name sibling alternatives (e.g. add vs delete chart), so tool-level selection guidance is implicit rather than stated.

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?