Табуля

files_set_dropdown

Adds a dropdown (list data-validation) to a range: each cell gets a dropdown of allowed values. Provide either 'values' (an explicit list of strings) or 'source_range' (an A1 range whose cell values are the options) — exactly one. strict (default true): reject entries not in the list; false: warn but allow. Pass 'id' (from files_validations) to replace that rule; omit to create. Requires edit permission; does not change existing values. Signature: files_set_dropdown(file_uuid, range, values?|source_range?, sheet?, id?, strict?).

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

Input Schema

Name	Required	Description
`id`	No	Existing validation id to replace; omit to create a new one.
`range`	Yes	A1 range to add the dropdown to, e.g. 'B2:B100'.
`sheet`	No	Sheet name (defaults to the first sheet).
`strict`	No	Reject values not in the list (default true); false warns but allows.
`values`	No	Explicit list of allowed options. Use this OR source_range.
`file_uuid`	Yes
`source_range`	No	A1 range whose cell values are the options. Use this OR values.

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

Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds the substantive context an agent actually needs: it requires edit permission, it explicitly does not change existing cell values, and strict=true (the default) rejects non-list entries while false merely warns. The replace-vs-create semantics via 'id' also explain the non-idempotent behavior declared in annotations.

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-loaded with the effect and the mutual-exclusivity rule, then defaults and replacement semantics, all in one dense paragraph with no filler. The trailing 'Signature:' line mostly restates the input schema and is the one mildly redundant element.

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 7-parameter mutation tool with an output schema, the description covers purpose, option sourcing, defaults, replacement workflow, and the permission requirement. Nothing an agent needs in order to call it 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 86%, so the baseline is 3. The description still adds value beyond the schema by stating the 'exactly one of values/source_range' invariant, the strict default behavior, and — most usefully — that the 'id' parameter comes from files_validations, which the schema does not say.

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 ('Adds a dropdown (list data-validation) to a range') and immediately defines the effect ('each cell gets a dropdown of allowed values'). This clearly separates it from the sibling validation setters (files_set_number_validation, files_set_custom_validation, files_set_checkbox) without needing their schemas.

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 concrete when-to-use rules: supply 'values' or 'source_range' but exactly one, and pass 'id' (sourced from files_validations) to replace versus omit to create. It does not explicitly say when to prefer this over the other validation-setting siblings, but the dropdown semantics make that largely self-evident.

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?