Табуля

files_get_info

Read-onlyIdempotent

Returns metadata for a single Tabulya spreadsheet file: name, spaceId, createdDate, updatedDate, the latest saved sequenceNumber, and your canView/canEdit permissions. Use to inspect one file before reading or editing it (files_list discovers many; this targets one by uuid). Read-only. Signature: files_get_info(file_uuid).

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

Input Schema

Name	Required	Description	Default
`file_uuid`	Yes	UUID of the file to inspect.

Output Schema

Name	Required	Description	Default
`name`	Yes
`uuid`	Yes
`canEdit`	Yes
`canView`	Yes
`spaceId`	Yes
`createdDate`	Yes
`updatedDate`	Yes
`sequenceNumber`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful behavioral context by listing the returned metadata fields, including sequenceNumber and canView/canEdit permissions, without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single tightly structured paragraph with the purpose and usage guidance front-loaded. Every sentence contributes either identification, scope, alternative selection, or return-content context.

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, rich annotations, and full schema coverage for the sole parameter, the description is complete for correct selection and invocation. It adds context about what metadata is returned and when to prefer this over files_list.

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 description coverage is 100%, so the file_uuid parameter is already fully documented. The description mentions the signature and that it targets one file by uuid, but does not add syntax or format details beyond 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 description uses a specific verb and resource: returns metadata for a single Tabulya spreadsheet file. It explicitly distinguishes this from files_list by noting that files_list discovers many while this targets one by uuid.

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?

It states exactly when to use the tool: to inspect one file before reading or editing it. It also names the alternative, files_list, and explains the selection condition: discovering many versus targeting one by uuid.

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?