Skip to main content
Glama

Datasource Add To Report

datasource_add_to_report

Attaches an existing datasource to a report, assigns its report alias, and verifies the report lists it as attached; repeat calls are idempotent.

Instructions

Add an existing datasource to the report (Add data > My data sources): names it in the report's datasourceAlias and verifies the report lists it as attached. Idempotent. Remove with datasources_remove_from_report.

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_add_to_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idNo
datasource_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive write. The description adds real behavioral context beyond them: it is idempotent, it writes a name into the report's datasourceAlias, and it verifies the report lists the datasource as attached. It does not mention permission requirements or failure modes, 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.

Conciseness5/5

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

Two short sentences plus a one-word idempotency note; the core action and its effect are front-loaded, and the removal pointer is placed last where it does not interrupt the primary instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 mutation is annotated as non-destructive. The remaining gap is the report_id parameter's defaulting behavior and any permission expectations, which are relevant for correct invocation.

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% for two parameters, so the description must carry the burden. It only obliquely clarifies datasource_id (an existing datasource being attached) and says nothing about report_id or its null default (presumably the current report), leaving the most ambiguous parameter unexplained.

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 and resource ("Add an existing datasource to the report"), anchors it to the product UI path (Add data > My data sources), and names the inverse operation, so it is clearly distinguishable from siblings like datasources_remove_from_report or datasource_create_bigquery.

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?

"Add an existing datasource" implicitly scopes usage to already-created datasources (not creation), and the definition points to datasources_remove_from_report as the counterpart for undoing the attachment. It stops short of stating exclusions or prerequisites (e.g., what happens if the datasource is already attached), so it is clear but not fully exhaustive.

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