Simpler.Asia

spreadsheet_file_update

Edit a spreadsheet file's metadata — title, tags, folder_id, or the AI-analysis fields — without touching the underlying R2 object. r2_key and source are birth facts: including either field in the call at all, even set to its current value, is refused — re-upload as a new file to change custody or provenance. Moving folder_id re-verifies the target folder belongs to your tenant. NEXT: spreadsheet_file_read to confirm the change landed.

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": {
      "id": "<id>"
    },
    "name": "spreadsheet_file_update"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The spreadsheet_file id (spreadsheet_file_list shows them).
`tags`	No
`title`	No
`r2_key`	No
`source`	No
`ai_prompt`	No
`file_size`	No
`folder_id`	No
`row_count`	No
`deleted_at`	No
`sheet_count`	No
`sheet_names`	No
`column_count`	No
`analysis_summary`	No
`last_analyzed_at`	No
`original_filename`	No
`expected_updated_at`	No	Optional compare-and-set guard: the updated_at you last read. Mismatch returns CONFLICT with the current value.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, it discloses important behavioral constraints: the R2 object is not touched, r2_key and source are immutable birth facts, and moving folder_id triggers tenant verification. It also tells the agent how to verify the change landed.

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 front-loaded with the purpose, then presents the critical immutability rule, tenant check, and next step in a compact sequence. Every sentence adds operational value without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 17-parameter mutation tool with sparse schema descriptions, the definition covers the critical rules and follow-up behavior but leaves several updateable fields ambiguous. It is adequate for common title/tags/folder edits but not fully complete for the whole schema.

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 only 12% across 17 parameters, so the description must carry most parameter meaning. It usefully explains r2_key/source refusal, folder_id tenant re-verification, and categories of editable fields, but leaves many schema fields such as deleted_at, file_size, row_count, sheet_count, and original_filename unexplained.

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 — edit a spreadsheet file's metadata — and clarifies the key boundary that the underlying R2 object is untouched. It also distinguishes the operation from re-uploading a new file and from spreadsheet_file_read used for confirmation.

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?

It gives a clear usage context for metadata edits and explicitly says r2_key/source cannot be changed, directing the agent to re-upload instead. It also names spreadsheet_file_read as the follow-up confirmation step, though it does not explicitly compare against spreadsheet_file_create or delete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Simpler.Asia 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?