Табуля

files_set_number_validation

Adds a numeric data-validation to a range: the number must satisfy at least one constraint. Provide any of: min and/or max (inclusive bounds — a value passes if min<=v<=max), greater_than/less_than (STRICT exclusive bounds; both together express 'not between': valid when v<less_than OR v>greater_than), equals (list — value must equal one of these), not_equals (list — value must differ from all of these). At least one constraint required. require_integer (default false): only whole numbers pass, a fractional value fails regardless of the bounds (Excel's "whole" rule). strict (default true): reject invalid entries; false warns. Pass 'id' (from files_validations) to replace. Requires edit permission. Signature: files_set_number_validation(file_uuid, range, sheet?, id?, strict?, min?, max?, greater_than?, less_than?, equals?, not_equals?, require_integer?).

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

Input Schema

Name	Required	Description
`id`	No	Existing validation id to replace.
`max`	No	Maximum allowed value (inclusive).
`min`	No	Minimum allowed value (inclusive).
`range`	Yes	A1 range, e.g. 'B2:B100'.
`sheet`	No
`equals`	No	Value must equal one of these.
`strict`	No	Reject invalid entries (default true); false warns.
`file_uuid`	Yes
`less_than`	No	Value must be strictly less than this (exclusive).
`not_equals`	No	Value must differ from all of these. Cannot be combined with other constraints.
`greater_than`	No	Value must be strictly greater than this (exclusive).
`require_integer`	No	Only whole numbers pass; a fractional value fails regardless of the bounds.

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.3/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses substantive behavior: 'strict (default true): reject invalid entries; false warns', require_integer's Excel 'whole' rule failing fractional values regardless of bounds, replacement of an existing validation via 'id', and the permission gate. This is the kind of consequence-level detail annotations cannot express.

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?

Purpose and the most important constraint rule are front-loaded, and the dense parenthetical style suits a 12-parameter tool. The closing signature line duplicates every parameter already in the schema, adding length without new meaning.

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 and annotations covering safety, the description supplies what remains: constraint combination logic, defaults for strict/require_integer, replacement semantics, and the edit-permission prerequisite. Nothing an agent needs to invoke this correctly appears to be 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 cross-parameter rules the schema cannot encode: at least one constraint must be supplied, greater_than/less_than are STRICT exclusive and together express 'not between' (v<less_than OR v>greater_than), while min/max are inclusive. It largely restates individual parameter docs, so it adds real but not exhaustive value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource ('Adds a numeric data-validation to a range') and immediately characterizes the constraint model, so the agent knows exactly what operation this performs. It never names or contrasts with sibling validators such as files_set_text_validation or files_set_custom_validation, so it falls short of the 5 criteria for sibling differentiation.

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 establishes clear usage context (numeric validation on a range), states a hard prerequisite ('At least one constraint required'), notes permission requirements ('Requires edit permission'), and explains replacement via 'id' from files_validations. It gives no explicit when-not guidance or routing to the alternative validation tools, so it is strong context without exclusions.

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?