Skip to main content
Glama
mcp-server-sigma

mcp-server-sigma

Datasets Swap Data Model Source Elements

datasets_swap_data_model_source_elements

Swap source elements in a Sigma data model by mapping existing sources to replacements, with optional metric and column mappings.

Instructions

Swap data model source elements (Beta).

OpenAPI: POST /v2/dataModels/{dataModelId}/swapSourceElements (dataModels_swapDataModelSourceElements). Spec: https://help.sigmacomputing.com/openapi/sigma-rest-api.json source_mapping items require from and to; optional metricMapping and columnMapping.

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>",
      "source_mapping": "<source_mapping>"
    },
    "name": "datasets_swap_data_model_source_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_model_idYes
source_mappingYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description carries a lighter burden. It usefully adds the Beta status and the required shape of source_mapping entries, but says nothing about what a swap actually does to existing elements, whether it is reversible, or whether precondition validation can fail — meaningful gaps for a mutation.

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?

Two short paragraphs, front-loaded with the capability, then the endpoint anchor and the parameter constraint. The OpenAPI spec URL is somewhat boilerplate but earns its place as a pointer to the full request body, and no sentence is redundant.

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 the annotations cover the safety profile. However, for a Beta mutation with a polymorphic array parameter, the description should still clarify what a swap accomplishes (e.g. remapping a source element to another), whether it is atomic, and how it differs from the sibling swap endpoints.

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?

Schema description coverage is 0% and source_mapping is an untyped array of additionalProperties objects with no declared inner fields, so the schema alone tells an agent nothing. The description compensates well by naming the required `from`/`to` keys and the optional `metricMapping` and `columnMapping` keys, which is the single most valuable piece of information here; only data_model_id goes unexplained, though it is self-evident from the endpoint path.

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 source elements") and anchors it to an HTTP endpoint (POST /v2/dataModels/{dataModelId}/swapSourceElements), so the operation is unambiguous on its own. What it does not do is distinguish this from the near-identical siblings datasets_swap_data_model_sources, datasets_swap_data_model_connections, and elements_swap_workbook_source_elements — an agent must guess how "source elements" differs from "sources" or "connections".

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 mention of alternatives despite a crowded sibling set of swap operations. The only context offered is the OpenAPI reference link, which is documentation routing rather than selection guidance.

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