Skip to main content
Glama

Datasources Remove From Report

datasources_remove_from_report
Destructive

Removes a datasource from a report by dropping its alias and claim, without deleting the datasource. Refused while components, filters, blends or parameters still use it.

Instructions

Remove a datasource from the report (Manage added data sources > Remove): drops its datasourceAlias and the report's claim. Refused while components, filters, blends or parameters use it. The datasource itself is not deleted.

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": "datasources_remove_from_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
datasource_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description's real contribution is scoping the blast radius: it drops the datasourceAlias and the report's claim, and explicitly leaves the datasource intact. However, it never discloses the dry_run parameter's default of true, meaning a default call performs no actual removal – a major behavioral fact for a destructive tool.

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 tight sentences, front-loaded with the action and UI anchor, followed by the refusal condition and the non-deletion clarification. No filler; the only omission is the parameter behavior the tool needs.

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?

Safety and scope are well covered for a destructive mutation, and an output schema exists so return values need no explanation. The significant remaining gap is that an agent is not told the operation defaults to a dry run, nor what report_id null means, which affects whether calling it has any effect.

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 three parameters, yet the description explains none of them: datasource_id, report_id (nullable, default null), and dry_run are never mentioned. The unmentioned dry_run default of true is especially consequential here, since it changes whether the mutation happens at all.

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?

Names a specific verb and resource ('Remove a datasource from the report'), maps it to the exact UI location (Manage added data sources > Remove), and pre-empts confusion with datasource deletion by stating 'The datasource itself is not deleted.' This distinguishes it cleanly from the sibling datasource_add_to_report.

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?

Gives a concrete precondition for failure: the removal is 'Refused while components, filters, blends or parameters use it,' which tells an agent when not to call it or how to interpret a rejection. It stops short of naming the alternative tool for those situations or stating how to resolve dependency conflicts.

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