mcp-server-sigma

Workbooks Copy Workbook To Member

workbooks_copy_workbook_to_member

Copy a workbook to a specific member's My Documents folder, with an optional new name for the copied workbook.

Instructions

Copy a workbook into a member's My Documents folder.

name: Optional name for the copied workbook. Defaults to the original workbook name.

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": {
      "workbook_id": "<workbook_id>",
      "member_id": "<member_id>"
    },
    "name": "workbooks_copy_workbook_to_member"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`member_id`	Yes
`workbook_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.4Oct 17, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already disclose that this is a non-destructive write operation with open-world effects. The description adds useful behavioral context: the copied workbook lands in the target member's My Documents folder and the name defaults to the original workbook name. It does not cover permission or authorization requirements for writing into another member's folder.

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 two short sentences, front-loads the core action, and contains no filler. The name-default detail is placed cleanly after the primary purpose.

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?

An output schema exists, so return values need not be described, and annotations cover mutation safety. However, the description omits authorization context for copying into another member's folder and provides no semantics for two of three parameters, leaving clear gaps for a write operation with open-world scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter semantics. It only clarifies the optional name parameter's default behavior, leaving member_id and workbook_id meaning to inference from their names alone.

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 gives a specific verb ('Copy') and resource ('a workbook'), plus a precise destination ('a member's My Documents folder'). This scoping distinguishes it from siblings like workbooks_duplicate_workbook and workbooks_create_workbook.

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

Usage Guidelines2/5

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

The description states what the tool does but gives no when-to-use guidance, no prerequisites, and no alternatives. It never mentions when to choose this over duplicating or creating a workbook.

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

Deploy Server