Skip to main content
Glama
mcp-server-sigma

mcp-server-sigma

Datasets Swap Data Model Connections

datasets_swap_data_model_connections

Swap a data model's source connections by mapping existing connection IDs to replacement IDs, with optional table and path updates.

Instructions

Swap data model connections (Beta).

OpenAPI: POST /v2/dataModels/{dataModelId}/swapConnections (dataModels_swapDataModelConnections). Spec: https://help.sigmacomputing.com/openapi/sigma-rest-api.json connection_mapping items require fromId and toId; optional swapTables and paths.

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": {
      "data_model_id": "<data_model_id>",
      "connection_mapping": "<connection_mapping>"
    },
    "name": "datasets_swap_data_model_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_model_idYes
connection_mappingYes
copy_input_table_dataNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds only '(Beta)' and an endpoint reference; it does not explain what swapping actually does to existing connections or tables, whether it is reversible, or what permissions are required for a mutation of this kind.

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?

Short and front-loaded: purpose first, then API reference, then the parameter note. The OpenAPI operation name and spec URL are reference-style filler for an agent that already has the schema, but they are compact and not misleading.

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 explained, and the annotations cover the safety profile. Still, for a Beta mutation that rewires data model connections, the definition says nothing about consequences, ordering, or the meaning of copy_input_table_data, leaving meaningful gaps for correct invocation.

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 0%, so the description carries the burden, and it partially does: it documents the nested connection_mapping item fields (required fromId/toId, optional swapTables/paths), which is real value over an untyped array of objects. It leaves data_model_id undocumented and completely ignores copy_input_table_data, whose null default and effect on materialized table data are non-obvious.

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 states a specific verb and resource ('Swap data model connections') and pins it to a concrete endpoint (POST /v2/dataModels/{dataModelId}/swapConnections). However, it never distinguishes this from close siblings such as datasets_swap_data_model_sources or datasets_swap_data_model_source_elements, so an agent must infer which swap variant to pick.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The only contextual hint is the '(Beta)' tag, which does not tell the agent when this tool is the right choice over the other swap tools in the catalog.

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

Deploy Server

Other Tools