Табуля

files_text_formats

Read-onlyIdempotent

Reads the cell formatting in an A1 range (the inverse of files_format), so you can inspect existing styles before changing them. Returns one entry per cell that has a non-default format: { cell (A1), and the set properties among bold/italic/underline/strikethrough/text_color/fill_color/align/vertical_align/wrap/number_format/negative/decimals/currency_symbol/numeric_commas/custom_format/date_time/font_size } — the same vocabulary files_format accepts, so a read format can be re-applied. custom_format holds an ECMA-376 number format code in the invariant (English) notation and takes precedence over the discrete tokens when both are present. Read-only; reflects the file's latest live state. Signature: files_text_formats(file_uuid, range, 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>",
      "range": "<range>"
    },
    "name": "files_text_formats"
  }
}

Input Schema

Name	Required	Description
`range`	Yes	A1 range to inspect, e.g. 'A1:H50'.
`sheet`	No	Sheet name (defaults to the first sheet).
`file_uuid`	Yes

Output Schema

Name	Required	Description	Default
`count`	Yes
`formats`	Yes
`file_uuid`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial value: it discloses the return shape (one entry per non-default cell), the property vocabulary, custom_format precedence over discrete tokens, ECMA-376 invariant notation, and that results reflect the file's latest live state.

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 purpose and inverse relationship are front-loaded and every clause carries information, but the long enumeration of format tokens and the trailing 'Signature:' line make it denser than strictly necessary for one paragraph.

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?

For a read tool with full annotations and an output schema, the description covers purpose, result shape, token vocabulary, and precedence rules. Nothing an agent needs in order to call and interpret it is missing.

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 67% and the description's signature line only repeats the parameter names, adding little beyond what the schema already documents for range ('A1 range to inspect') and sheet (defaults to first sheet). file_uuid is undocumented in both places, so the description does not fully compensate.

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?

Specific verb+resource: 'Reads the cell formatting in an A1 range', with explicit scope (formatted cells only) and an explicit contrast to the sibling files_format ('the inverse of'). An agent can distinguish it from files_format or files_get_info without opening a schema.

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

Usage Guidelines5/5

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

States both the alternative (files_format) and the condition that selects this tool: 'so you can inspect existing styles before changing them'. It also notes the output vocabulary matches files_format so a read format can be re-applied, which is a concrete usage rule.

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?