Skip to main content
Glama

dashy_keys

Destructive

Retrieve or replace one top-level Dashy config key—pageInfo, appConfig, sections, or pages—with dry-run previews and confirmation-gated writes that overwrite rather than merge.

Instructions

Get or replace one top-level key: pageInfo, appConfig, sections, or pages. Replace overwrites that key. It does not merge. Writes run only when confirm is true and DASHY_ALLOW_WRITES=true. Actions: get, replace. Listing sections is get with key sections.

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

Input Schema

NameRequiredDescriptionDefault
keyNoTop-level config key.
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.
filenameNoConfig basename in the user-data directory, for example conf.yml.
replacementNoReplacement for one top-level key. pageInfo and appConfig are objects. sections and pages are arrays. This replaces the key. It does not merge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations flag destructiveHint=true and readOnlyHint=false, but the description adds behavior annotations cannot express: replacement overwrites the key and does not merge, and there is a dual gate (confirm plus an environment flag) with a no-op dry-run when confirm is absent. This is precisely the mutation-risk context an agent needs before calling.

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?

Six short sentences, front-loaded with purpose, then the overwrite rule, then the write gate, then action enumeration. Every line carries operational weight; even the short 'Actions: get, replace' is a cheap scannable confirmation of the enum.

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?

For a 5-parameter mutation tool with no output schema, the description covers purpose, risk, and gating well. The remaining gap is that nothing is said about what 'get' returns or how filename interacts with the operation, which is the one thing an agent must discover from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3; the description nonetheless adds the action×key interplay ('Listing sections is get with key sections') and restates the non-merge contract for the replacement payload, which the schema only hints at. It does not add format detail for filename or replacement shape beyond the schema, so it stops short of a 5.

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 first sentence gives a specific verb pair (get/replace) and a concrete resource (one top-level key) with the full key enum spelled out, so an agent knows exactly what the tool operates on. It does not name sibling tools like dashy_config or dashy_sections directly, but the closing note routes 'listing sections' to get+key=sections, which is the critical disambiguation.

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?

Explicit conditions are given for the risky path: writes require confirm=true AND DASHY_ALLOW_WRITES=true, and omitting confirm yields a dry-run that sends nothing. The sections-listing mapping tells the agent when to use this rather than a section-oriented sibling. It stops short of stating outright exclusions (e.g., when to prefer dashy_config) but the operational guidance is clear.

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