Skip to main content
Glama
ADIKANT

datalens-dev-mcp

by ADIKANT

Run Live Maintenance Update

dl_run_live_maintenance_update

Plans and validates live maintenance updates for DataLens dashboards using guarded execution and runtime evidence to ensure safe application of changes.

Instructions

Plan and validate Delta v8 maintenance from supplied guarded execution and runtime evidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentNointent input.fix_existing
publishNoRequest publish behavior.
approvedNoCodex/tool approval flag for guarded safe apply. Defaults to false.
target_urlNo
workbook_idNoDataLens workbook id.
allow_createNoallow_create input.
cleanup_modeNocleanup_mode input.plan_only
dashboard_idNoDataLens dashboard id.
project_rootNoLocal project root..
target_tab_idNotarget_tab_id input.
changed_objectsNochanged_objects input.
guarded_requestsNoguarded_requests input.
maintenance_modeNomaintenance_mode input.quick_visible_patch
target_object_idsNotarget_object_ids input.
baseline_dashboardNobaseline_dashboard input.
proposed_dashboardNoproposed_dashboard input.
safe_apply_actionsNosafe_apply_actions input.
runtime_gate_evidenceNoruntime_gate_evidence input.
baseline_snapshot_pathNobaseline_snapshot_path input.
create_necessity_proofNocreate_necessity_proof input.
source_budget_evidenceNosource_budget_evidence input.
metadata_evidence_pathsNometadata_evidence_paths input.
non_rendering_exemptionNonon_rendering_exemption input.
saved_readback_evidenceNosaved_readback_evidence input.
browser_runtime_requiredNobrowser_runtime_required input.
publish_from_saved_evidenceNopublish_from_saved_evidence input.
published_readback_evidenceNopublished_readback_evidence input.
saved_runtime_gate_evidenceNosaved_runtime_gate_evidence input.
source_availability_artifactNosource_availability_artifact input.
safe_apply_execution_evidenceNosafe_apply_execution_evidence input.
published_runtime_gate_evidenceNopublished_runtime_gate_evidence input.
Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose whether the tool mutates state, requires approval (despite 'approved' parameter), or is read-only. Behavioral traits are missing.

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?

A single concise sentence without redundancy. It is front-loaded and efficient, though it could be longer given tool complexity. Earns its space but lacks depth.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 31 parameters, no output schema, and numerous siblings, the description is woefully incomplete. It explains neither return values, side effects, nor how to use the parameters, leaving the agent underinformed.

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 97%, so the schema already documents parameters. The tool-level description adds no parameter-level meaning; baseline 3 is appropriate as description does not degrade quality.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb-resource pair ('Plan and validate Delta v8 maintenance') but is vague regarding exact scope. It does not distinguish from sibling tools like dl_build_payload_plan or dl_create_safe_apply_plan, making purpose ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The description provides no context, prerequisites, or exclusions, leaving the agent without decision-support for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ADIKANT/datalens-dev-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server