Skip to main content
Glama

sheets_insert_date

Insert dates into Google Sheets with locale-aware formatting and automatic format detection. Supports various date formats and relative dates.

Instructions

Insert properly formatted dates in Google Sheets with locale support and automatic detection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate to insert (supports various formats: YYYY-MM-DD, DD.MM.YYYY, MM/DD/YYYY, or relative dates like "today", "tomorrow")
rangeYesThe A1 notation range to insert the date (e.g., "Sheet1!A1")
formatNoDate format preference (locale=spreadsheet locale, iso=YYYY-MM-DD, us=MM/DD/YYYY, eu=DD.MM.YYYY)locale
autoDetectNoAutomatically detect and parse date format (default: true)
useEUFormatNoUse semicolon separator for EU locale sheets (auto-detected from user language/context if not specified)
spreadsheetIdYesThe ID of the spreadsheet (found in the URL after /d/)
Behavior3/5

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

With no annotations, the description carries full burden. It mentions proper formatting, locale support, and automatic detection, but does not disclose behavior on invalid dates, error handling, or whether existing cell content is overwritten.

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 a single, well-structured sentence that conveys the tool's core purpose without unnecessary words. It is appropriately concise.

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

Completeness2/5

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

Given the tool has 6 parameters (3 required) and no output schema, the description is too brief. It does not explain return values, error scenarios, or how the tool integrates with the spreadsheet (e.g., overwriting behavior).

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 100%, so the baseline is 3. The description adds some context about locale and auto-detection, but does not significantly enhance understanding beyond the parameter descriptions.

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 clearly states the action (insert), the resource (dates in Google Sheets), and key features (locale support, automatic detection). It effectively distinguishes this tool from siblings like sheets_update_values or sheets_append_values.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for inserting dates but provides no explicit guidance on when to use it versus alternatives, nor does it mention when not to use it. No comparisons or exclusions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/freema/mcp-gsheets'

If you have feedback or need assistance with the MCP directory API, please join our Discord server