Skip to main content
Glama
Sign In

Табуля

by ru.tabulya
OverviewDiscussionsAdmin

files_format

Applies cell formatting to an A1 range in a Tabulya spreadsheet (bold/italic/underline/strikethrough, text & fill color, horizontal & vertical alignment, wrapping, font size, number format like currency/percent/accounting/text, thousands separators, date/time display format, and custom_format — an ECMA-376 number format code for anything the discrete tokens cannot express: section colors, conditions, fractions, padding, literals). Codes are stored in the invariant (English) notation, the same one files_text_formats returns. Pass clear:true to remove ALL formatting from the range. Requires edit permission; non-destructive (does not change values). Pass only the properties you want to change. Applied through the collaboration server. Signature: files_format(file_uuid, range, sheet?, clear?, bold?, italic?, underline?, strikethrough?, text_color?, fill_color?, align?, vertical_align?, wrap?, number_format?, decimals?, currency_symbol?, negative?, numeric_commas?, custom_format?, date_time?, font_size?).

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_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
boldNo
wrapNo
alignNoHorizontal alignment.
clearNoRemove ALL formatting from the range (other properties are ignored when true).
rangeYesA1 range to format, e.g. 'A1:C10', 'B:B' (whole column).
sheetNoSheet name (defaults to the first sheet).
italicNo
decimalsNoNumber of decimal places.
negativeNoNegative-value style for number_format='number' and 'currency': minus (default), minus_red (red), red (no sign, red), parentheses, parentheses_red.
date_timeNoDate/time display format string (strftime-style, e.g. '%Y-%m-%d' or '%-m/%-d/%Y %-I:%M %p').
file_uuidYes
font_sizeNoFont size in points.
underlineNo
fill_colorNoBackground hex color.
text_colorNoHex color, e.g. '#1F77B4'.
custom_formatNoExcel (ECMA-376) number format code, e.g. '#,##0.00;[Red](#,##0.00)', '0.00%', '# ??/??', '_("$"* #,##0.00_);_("$"* (#,##0.00);_("$"* "-"??_);_(@_)'. Use it for anything the discrete number_format tokens cannot express: section colors, conditions, fractions, fill/pad characters, literal text. Overrides number_format and date_time. Separators are rendered in the Russian locale (space for thousands, comma for decimals) like the rest of the grid.
number_formatNoNumber display format. 'text' keeps input as raw text (no number/date inference); 'accounting' is currency with negatives in parentheses and zero as a dash.
strikethroughNo
numeric_commasNoShow thousands separators (e.g. 1,234,567).
vertical_alignNoVertical alignment.
currency_symbolNoCurrency symbol when number_format='currency' or 'accounting' (default '$').

Output Schema

NameRequiredDescriptionDefault
rangeYes
file_uuidYes
sequence_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that edit permission is required, that the operation is non-destructive to values, that it is applied through the collaboration server, and that codes are stored in invariant notation. The safety profile (destructive=false, readOnly=false) is already in annotations, so this extra context is meaningful.

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 behavior-critical facts (clear:true, permissions, non-destructive) are front-loaded, followed by a dense but purposeful parenthesis of properties and a signature line. It is long but nearly every clause carries information; only the trailing signature duplicates schema content.

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?

Given an existing output schema and rich annotations, the description fills the key gaps: permission requirements, clear flag semantics, precedence of custom_format, and locale rendering. It is nearly complete for a 21-parameter tool, with only minor ambiguity around alternative tooling left unaddressed.

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 71%, and the description adds real meaning beyond it—explaining custom_format precedence ('Overrides number_format and date_time'), the locale rendering of separators, and the purpose of discrete tokens vs. custom_format. A few params (file_uuid, bold, italic, underline) get no elaboration, but the tricky ones are well covered.

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 ('Applies cell formatting') applied to a specific resource (an A1 range in a Tabulya spreadsheet), and enumerates the supported property families. This clearly distinguishes it from siblings like files_borders, files_conditional_formats, and files_set_conditional_format.

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 concrete operational guidance: 'Pass only the properties you want to change' and 'Pass clear:true to remove ALL formatting.' However, it does not explicitly route the agent away from neighboring tools (e.g., when to prefer files_borders or conditional formats over this), leaving some inference to the reader.

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

All Табуля toolsInspect
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