Табуля

files_set_datetime_validation

Adds a date/time data-validation to a range. Constraints (the value passes if it satisfies at least one): date_min/date_max (inclusive date bounds; both together = 'between'), date_equals/date_not_equals (date lists), date_after/date_before (STRICT exclusive bounds; both together express 'not between'), time_min/time_max (inclusive time bounds), time_equals/time_not_equals (time lists). Dates are 'YYYY-MM-DD', times 'HH:MM' or 'HH:MM:SS'; date-time cell values are compared to date constraints by day. Flags: require_date/require_time (the value must include a date/time; set automatically when date/time constraints are given), prohibit_date/prohibit_time (must NOT include one). At least one flag or constraint required. strict (default true): reject invalid entries; false warns. Pass 'id' (from files_validations) to replace. Requires edit permission. Signature: files_set_datetime_validation(file_uuid, range, sheet?, id?, strict?, require_date?, require_time?, prohibit_date?, prohibit_time?, date_min?, date_max?, date_equals?, date_not_equals?, date_after?, date_before?, time_min?, time_max?, time_equals?, time_not_equals?).

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

Input Schema

Name	Required	Description
`id`	No	Existing validation id to replace.
`range`	Yes	A1 range, e.g. 'C2:C100'.
`sheet`	No
`strict`	No	Reject invalid entries (default true); false warns.
`date_max`	No	Latest allowed date, inclusive ('YYYY-MM-DD').
`date_min`	No	Earliest allowed date, inclusive ('YYYY-MM-DD').
`time_max`	No	Latest allowed time, inclusive ('HH:MM' or 'HH:MM:SS').
`time_min`	No	Earliest allowed time, inclusive ('HH:MM' or 'HH:MM:SS').
`file_uuid`	Yes
`date_after`	No	Date must be strictly after this (exclusive, 'YYYY-MM-DD').
`date_before`	No	Date must be strictly before this (exclusive, 'YYYY-MM-DD').
`date_equals`	No	Date must equal one of these ('YYYY-MM-DD').
`time_equals`	No	Time must equal one of these ('HH:MM' or 'HH:MM:SS').
`require_date`	No
`require_time`	No
`prohibit_date`	No
`prohibit_time`	No
`date_not_equals`	No	Date must differ from all of these ('YYYY-MM-DD'). Cannot be combined with other date constraints.
`time_not_equals`	No	Time must differ from all of these ('HH:MM' or 'HH:MM:SS'). Cannot be combined with other time constraints.

Output Schema

Name	Required	Description	Default
`range`	Yes
`file_uuid`	Yes
`sequence_number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: strict defaults to true and false only warns, require_date/require_time are set automatically when date/time constraints are supplied, date-time cell values are compared by day, and an existing validation can be replaced by passing 'id'. These are material behavioral details not captured by readOnlyHint, destructiveHint, or idempotentHint.

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 content is front-loaded and organized around constraints, formats, flags, and replacement behavior. However, the final signature listing repeats all parameter names and optionality already present in the input schema, which is redundant and makes the description longer than necessary.

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?

Given the tool's complexity, this description covers the essential behavioral and parameter semantics: constraint combinations, strictness, automatic flags, permissions, and replacement. An output schema exists, so return values need not be explained, and the remaining omission of the optional 'sheet' parameter's meaning is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 19 parameters and only 68% schema description coverage, the description carries substantial semantic load. It explains the inclusive vs strict-exclusive date/time constraints, the OR-style 'at least one' pass condition, the automatic require flags, accepted date/time formats, and replacement behavior via 'id'.

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 opens with a specific verb and resource: 'Adds a date/time data-validation to a range.' It clearly distinguishes this tool from sibling validation tools such as number, text, dropdown, and custom validation by naming the date/time domain explicitly.

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?

The description gives useful operational context: at least one flag or constraint is required, 'id' from files_validations replaces an existing validation, and edit permission is required. It does not explicitly compare this tool to alternatives like files_set_number_validation or files_set_custom_validation, so it stops short of full when/when-not guidance.

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?