Skip to main content
Glama

Datasource Credentials Set

datasource_credentials_set
Destructive

Switches a Datastudio datasource to Service Account Credentials, using an explicit account or environment template, with a preview by default before applying the change.

Instructions

Switch a datasource to Service Account Credentials.

Without service_account, the DATASTUDIO_SERVICE_ACCOUNT_TEMPLATE environment variable names it ({project} = the BigQuery project the source runs in); with neither, the call is refused. datasource_get shows the current credentials. The editing user needs Service Account User on the account. Preview by default; the change is journaled and read back but not restorable, because owner's credentials belong to a person and cannot be replayed.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
datasource_idYes
service_accountNo
allow_shared_sourceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the destructive annotation, the description discloses that the change is journaled and read back but not restorable because owner credentials cannot be replayed. It also explains the preview default and the refusal behavior, giving the agent enough context to understand the mutation's irreversibility.

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?

The description is front-loaded with the core action and then adds relevant operational details without much waste. The use of line breaks and dense clauses makes it slightly harder to scan, but every sentence contributes useful context.

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?

For a destructive mutation tool with an output schema, the description covers the main behavior, permission requirement, fallback, refusal, and irreversibility. However, it remains incomplete because three of five input parameters are not explained anywhere, given the 0% schema description coverage.

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 document the five parameters, but it only explains service_account fallback behavior and implies dry_run via 'Preview by default'. It leaves datasource_id, report_id, and allow_shared_source entirely undocumented, which is a significant gap.

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: switching a datasource to Service Account Credentials. It distinguishes this from datasource_get by noting that datasource_get shows current credentials, but it does not explicitly differentiate from other sibling mutation tools.

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?

It gives clear context for when the call applies and notes the fallback via DATASTUDIO_SERVICE_ACCOUNT_TEMPLATE and the refusal condition when neither is provided. It also states the required Service Account User permission, though it does not explicitly name alternatives for other credential-related operations.

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