Skip to main content
Glama

Datasource Parameters Delete

datasource_parameters_delete
Destructive

Delete unused datasource parameters after dependency checks; previews, journaling and read-back guard each removal so formulas and shared reports stay intact.

Instructions

Delete unused datasource parameters after conservative dependency checks.

References in datasource formulas and the full configured report block deletion. Shared sources additionally require acceptance that external consumers cannot be inventoried. Publication is previewed, guarded, journalled, read back and undoable.

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>",
      "parameter_keys": "<parameter_keys>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "datasource_parameters_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
datasource_idYes
parameter_keysYes
allow_shared_sourceNo
expected_fingerprintYes
allow_unscanned_shared_consumersNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the safety profile is known; the description adds genuinely useful behavior beyond that — dependency gating, a preview/dry-run stage, journaling, read-back and undoability. The phrasing 'guarded, journalled, read back and undoable' is somewhat buzzword-level rather than operational, 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.

Conciseness4/5

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

Three sentences, front-loaded with the core action before the constraints, with no filler sentences. Some compression wording ('guarded, journalled, read back') costs a little precision without adding much information.

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 blocking conditions are well covered. However, for a destructive tool with a required concurrency-style parameter (expected_fingerprint) undocumented in both schema and description, the definition leaves a real gap an agent must guess at.

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% across 7 parameters, so the description must compensate, and it only partly does: 'shared sources additionally require acceptance that external consumers cannot be inventoried' explains the shared-source acceptance flags, and 'previewed' hints at dry_run. The required expected_fingerprint (likely a concurrency/version guard), report_id, and parameter_keys go entirely unexplained.

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 opens with a specific verb and resource ('Delete ... datasource parameters') plus a scope qualifier ('unused ... after conservative dependency checks'), which distinguishes it from datasource_parameters_upsert and datasource_parameters_list. It does not explicitly name an alternative, but the action and target are unambiguous.

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 concrete conditions that block deletion (references in datasource formulas, the full configured report) and an extra precondition for shared sources, which effectively tells the agent when this tool will refuse. It stops short of routing guidance (e.g. when to prefer dry_run first or how it relates to upsert), so it is clear context without explicit alternatives.

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