Simpler.Asia

spreadsheet.create_with_content

Create a spreadsheet in the user's library from CSV content in ONE call: the platform stores the bytes (honest text/csv) and registers the file row. Free — storage costs nothing; only AI lanes bill. Returns the file row including its id. Refuses: VALIDATION_ERROR when title or csv_content is empty (send both), VALIDATION_ERROR when csv_content is over 10 MB (split it into smaller files), NOT_FOUND when folder_id names no folder in this workspace (call spreadsheet_folder_list, or leave folder_id out), FORBIDDEN when your role is viewer or your token is read-only (ask the owner for the member role, or connect with the 'mcp' scope). Nothing is stored when it refuses. NEXT: spreadsheet_file_list to see the library.

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": {
      "title": "<title>",
      "csv_content": "<csv_content>"
    },
    "name": "spreadsheet.create_with_content"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Library title for the file (≤255 chars).
`folder_id`	No	Optional spreadsheet_folder id to file it under.
`csv_content`	Yes	The complete CSV content (first row = headers). At most 10 MB.

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?

The description discloses key behavior beyond the annotations: it stores bytes, registers a file row, returns the file row including its id, charges no storage cost, and does not store anything when validation or permission checks fail. It also surfaces auth-related failure modes and their remedies.

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 description is front-loaded with the operation and return value, then follows with cost, refusal modes, and next step. It is information-dense and mostly earns its length, though the refusal list is lengthy and some details repeat schema constraints.

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 a mutating file-creation tool with only a readOnlyHint annotation and no output schema, the description supplies the missing context: side effects, cost, return value, validation and permission failures, no-write-on-refusal behavior, and a natural next step.

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 100%, so the schema already defines title, folder_id, and csv_content with constraints. The description adds practical parameter meaning by tying empty title/csv_content, oversized csv_content, and invalid folder_id to specific error outcomes and remedies.

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 description clearly states a specific verb and resource: create a spreadsheet in the user's library from CSV content in one call. It implies differentiation from other spreadsheet tools by emphasizing CSV content import, but it does not explicitly name or contrast with siblings such as spreadsheet_file_create.

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 clear context for when to use the tool: when creating a spreadsheet from CSV content in a single call. It also provides error-specific remedies such as splitting large CSV files or listing folders when folder_id is invalid, but it does not explicitly compare usage against sibling creation tools.

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?