WiseGrid MCP

add_rows

Add multiple rows to a WiseGrid sheet using column ID keys, with per-row validation results and success/failure counts for up to 2000 rows.

Instructions

Add rows to a sheet. Each item is a dict of cells keyed by column ID (as a string), e.g. {"101": "Acme Corp", "102": "2026-09-01"}.

Partial success: the response reports per-row results plus succeededCount and failedCount, so some rows can land while others fail validation. Maximum 2000 rows per call.

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": {
      "sheet_id": "<sheet_id>",
      "rows": "<rows>"
    },
    "name": "add_rows"
  }
}

Input Schema

Name	Required	Description	Default
`rows`	Yes
`sheet_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description fully carries the burden of behavioral disclosure. It explicitly notes partial success with per-row results and succeededCount/failedCount, and a hard limit of 2000 rows per call. These are critical behaviors beyond basic mutation semantics.

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 concise and well-structured: purpose, row format, then behavioral notes (partial success, limit). Every sentence adds value and there is no redundant fluff.

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

Completeness4/5

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

For a two-parameter mutation tool with no annotations and an output schema (not shown), the description adequately covers the input format, behavioral edge cases, and limit. Minor omissions like error handling for invalid sheet_id are acceptable given the tool's simplicity.

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?

The input schema provides zero parameter descriptions. The description compensates for the 'rows' parameter by explaining the dict structure keyed by column ID and providing an example. 'sheet_id' is not described but is self-explanatory from its name and the sheet context.

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 'Add rows to a sheet', a specific verb and resource, and provides an example of the expected input format. This distinguishes the tool from siblings like update_rows and delete_row by focusing on creation.

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 provides useful constraints (maximum 2000 rows, partial success behavior) but does not explicitly mention when to use this tool versus alternatives such as update_rows or delete_row. The primary usage is implied by the tool's name and purpose, but no exclusions or comparative guidance are given.

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

Deploy Server