Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__sheets_copy_tab_to

Copies one tab of a Google Sheets spreadsheet into another spreadsheet. Takes the source spreadsheet ID, the title of the tab to copy and the destination spreadsheet ID. The copy carries the tab's values, formulas and formatting and is added to the destination as a new tab, which Google names "Copy of "; nothing already in the destination is changed, and the source is left as it was. Returns the new tab's sheetId, title and position in the destination. The account needs edit access to the destination.

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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "title": "<title>",
      "destination_spreadsheet_id": "<destination_spreadsheet_id>"
    },
    "name": "gws-mcp__sheets_copy_tab_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the tab to copy, as sheets_get_metadata lists it
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
spreadsheet_idYesThe ID of the spreadsheet that holds the tab to copy
destination_spreadsheet_idYesThe ID of the spreadsheet the copy is added to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well past the annotations by disclosing the additive, non-destructive nature of the operation on both sides, the derived name Google assigns ('Copy of <title>'), and the authentication requirement. It also names the return payload (sheetId, title, position), compensating for the absent output schema.

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?

Four compact sentences, none wasted, with the action stated first and preconditions/caveats following. Every sentence adds new information rather than restating the name.

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 four-parameter mutation tool with no output schema, the description covers the action, the side effects, the naming convention, the return shape, and the permission requirement. An agent has everything needed to select and invoke it correctly.

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 coverage is 100%, so all four parameters already carry descriptions. The description restates the three required IDs and role of title, but adds only the derived copy-name convention; it does not explain why a tab title must be unique or how the optional account parameter interacts with access.

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 and resource: copying one tab from a source spreadsheet into a different destination spreadsheet. That scoping cleanly separates it from sheets_add_tab (new empty tab), sheets_rename_tab, and drive_copy_file (whole-file copy) without the reader opening any schema.

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 clear use context and a hard precondition — 'The account needs edit access to the destination' — and clarifies that the source is untouched and the destination is not otherwise modified. It stops short of naming alternatives (e.g. drive_copy_file for whole-workbook duplication) or stating when not to use it.

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

All DataToRAG toolsInspect
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