Skip to main content
Glama

dashy_sections

Destructive

Add, retrieve, update, or delete dashboard sections by index or exact name, with confirm-gated writes and dry-run previews to control Dashy configuration edits.

Instructions

Add, get, shallow-merge, or delete a dashboard section. sid is a zero-based index or an exact section name. Add needs document.name. Writes run only when confirm is true and DASHY_ALLOW_WRITES=true. Actions: add, get, update, delete.

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": {
      "action": "<action>"
    },
    "name": "dashy_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
sidNoSection index (0, 1, ...) or exact section name.
actionYesDashy operation to call.
confirmNoBoolean true runs the write when DASHY_ALLOW_WRITES is true. Omit it or pass false for a dry-run preview that sends nothing. The string true is rejected.
documentNoJSON object body. Section adds need name. Item adds need title.
filenameNoConfig basename in the user-data directory, for example conf.yml.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructive=true and readOnlyHint=false, but the description adds genuinely new context: the two-flag write gate (confirm + DASHY_ALLOW_WRITES) and the fact that omitting confirm produces a dry-run that sends nothing. The "shallow-merge" wording also signals that nested section content is merged rather than replaced wholesale, which matters 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?

Sentences are short and the write-gating constraint, the most consequential fact, arrives early. The trailing "Actions: add, get, update, delete" partially repeats the verb list from the first sentence, a minor redundancy.

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 four-action multiplexed tool with a nested free-form document object and no output schema, the description covers add's requirement and the write gate well. It never states that sid is needed for get, update, and delete (only action is required in the schema), and it says nothing about what get returns, leaving meaningful gaps.

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 coverage is 100%, so sid, confirm, document, and filename are already documented in the schema. The description restates sid's index-or-name semantics and adds the per-action body requirement for add, but adds little beyond that; baseline 3 applies when the schema carries the load.

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 opening sentence names specific verbs (add, get, shallow-merge, delete) against a concrete resource (dashboard section), and "shallow-merge" usefully distinguishes update from a full replace. It does not explicitly contrast itself with sibling tools like dashy_items, though "section" implies the distinction.

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

Usage Guidelines3/5

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

The description gives conditional usage for writes (confirm plus DASHY_ALLOW_WRITES) and notes that add needs document.name, which helps an agent decide how to call it. However, it never states when to pick this tool over dashy_items or dashy_config, leaving that routing to inference from the resource noun.

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