Skip to main content
Glama

Datasource Parameters Upsert

datasource_parameters_upsert
Destructive

Create or replace complete datasource parameter definitions losslessly, preserving roles, defaults, options, validation, and display metadata while guarding writes with fingerprints and preview.

Instructions

Create or replace complete datasource parameter definitions losslessly.

The definition is Data Studio's typed wire from datasource_parameters_list; roles, defaults, options, validation and display metadata are retained exactly. New parameter (Add a parameter): {"parametersModifiedByRoles": [{"key": 1, "value": {"name": K, "dataType": 1 text | 2 number | 4 boolean, "lock": 2, "options": [], "validation": {}, "defaultValue": [{"label": "0.9", "stringValue": "0.9"}]}}, the same under key 2 without label], "parameterDisplayConfiguration": {"name": K, "displayName": "...", "displayType": 1}}; values are strings for every type. Replacing a referenced parameter requires allow_in_use=true. Shared sources need explicit opt-in. Matching draft/published, fingerprint, full-report guard, preview, read-back and operation_restore apply to the datasource-atomic publish.

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": {
      "datasource_id": "<datasource_id>",
      "parameters": "<parameters>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "datasource_parameters_upsert"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
parametersYes
allow_in_useNo
datasource_idYes
allow_shared_sourceNo
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds real context beyond that — lossless retention of roles/defaults/validation/display metadata, fingerprint matching against draft/published, a full-report guard, and operation_restore for undoing the publish. The phrasing is compressed and cryptic in places ('datasource-atomic publish'), which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, which is good, but the body is a dense run-on mixing JSON payload examples with guard-rail jargon. Every element is arguably relevant, yet the prose would benefit from separation between payload format and operational preconditions.

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 mutation's guard rails are covered. Still, for a 7-parameter destructive tool at 0% schema coverage, the description leaves several parameters and the default dry_run=true preview behavior underspecified.

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 must carry parameter meaning. It does explain allow_in_use, allow_shared_source, the fingerprint requirement, and shows a concrete parameters payload example, but datasource_id, report_id, and the exact role of dry_run are never stated outright.

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 opening sentence states a specific verb and resource — 'Create or replace complete datasource parameter definitions losslessly' — which is enough to distinguish it from datasource_parameters_list and datasource_parameters_delete. It stops short of a 5 because the 'upsert is a full replacement of the parameter set' implication is only fully clarified later in the text.

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?

It points at datasource_parameters_list as the source of the wire format and states preconditions (allow_in_use=true when replacing a referenced parameter, explicit opt-in for shared sources), which is genuinely useful. However, it never says when to choose this over other datasource mutation tools, and it does not clarify when to pass dry_run=false versus previewing first.

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