Табуля

files_borders

Applies (or clears) cell borders on an A1 range. sides: which edges — all, inner, outer, horizontal, vertical, left, top, right, bottom, or clear (remove borders). line: line1 (thin, default), line2 (medium), line3 (thick), double, dotted, dashed. color: hex like '#000000' (default black). Requires edit permission; does not change values. Note: re-applying borders that exactly match the existing ones toggles them off. Signature: files_borders(file_uuid, range, sheet?, sides?, line?, color?).

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

Input Schema

Name	Required	Description
`line`	No	Line style (default 'line1' = thin).
`color`	No	Hex color '#RRGGBB' or '#RRGGBBAA' (default '#000000').
`range`	Yes	A1 range, e.g. 'A1:D5'.
`sheet`	No	Sheet name (defaults to the first sheet).
`sides`	No	Which edges to set (default 'all'); 'clear' removes borders.
`file_uuid`	Yes

Output Schema

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

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?

Adds real behavior beyond the annotations: edit-permission requirement, guarantee that cell values are untouched, and the subtle toggle rule ("re-applying borders that exactly match the existing ones toggles them off") which explains the non-idempotent semantics an agent would otherwise trip over.

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-loads the core action and the important toggle caveat, with tight sentences. Slightly overstuffed with enumerations already in the schema and a redundant signature line at the end.

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, the description doesn't need to explain return values, and it covers permissions, side-effects, defaults, and the non-idempotent toggle case. Nothing an agent needs to call this correctly is missing.

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 already 83%, but the description adds meaning: glossaries the enum values ("line1 (thin, default), line2 (medium), line3 (thick)"), restates defaults for line/color, and interprets sides='clear' as removal rather than a styling choice. The trailing signature is redundant with 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?

Opens with a specific verb+resource: "Applies (or clears) cell borders on an A1 range." This clearly separates it from neighboring tools like files_format (general formatting) and sheets_color (fill colors), so an agent can pick it 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?

Gives clear context: use it for border edges and styles, and use sides='clear' to remove borders. Also states the prerequisite ("Requires edit permission") and the non-goal ("does not change values"). It never names a sibling tool as an alternative, so it stops short of full when/when-not routing.

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?