Skip to main content
Glama

dashy_items

Destructive

Manage Dashy dashboard tiles by listing, adding, retrieving, shallow-merging, or deleting items in a section, with confirm-gated writes for controlled edits.

Instructions

List, add, get, shallow-merge, or delete a tile in a section. sid and iid are an index or an exact name or title. Add needs document.title. List accepts offset and limit applied after the fetch. Writes run only when confirm is true and DASHY_ALLOW_WRITES=true. Actions: list, 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_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
iidNoItem index or exact item title.
sidNoSection index or exact section name.
limitNoClient-side page size. Applied after the full list is fetched.
actionYesDashy operation to call.
offsetNoClient-side start index. Dashy has no page query. Omitted returns the full list.
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.9/5.0
Behavior5/5

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

Annotations only declare the operation is destructive and non-read-only; the description adds real substance beyond them: writes execute only when confirm is true AND DASHY_ALLOW_WRITES=true, confirm false is a no-op preview that sends nothing, and update performs a shallow merge rather than a replacement. That merge semantics detail is exactly the kind of behavior an agent cannot get from annotations.

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?

Front-loaded and dense, with each sentence carrying the operations, identifiers, pagination, or write gating. The trailing 'Actions: list, add, get, update, delete.' largely repeats the opening verb list, which is the one wasteful line.

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 an 8-parameter, multi-action, nested-object tool with no output schema, the description covers the write safety model, merge semantics, and identifier resolution well. It omits what get or list return and the filename parameter's role, leaving a small gap.

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 100%, so the schema already defines offset, limit, confirm, document and the identifier patterns. The description adds only modest meaning (add requires document.title; pagination is applied after the full fetch), much of which restates the schema's own wording.

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 the resource precisely ('a tile in a section') and enumerates the five operations (list, add, get, shallow-merge/update, delete), so the agent knows exactly what the tool handles. It stops short of explicitly contrasting itself with the sibling dashy_sections tool, leaving that distinction to be inferred from the word 'tile'.

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?

Usage context is implied through the action list and the write-gate sentence, but there is no explicit statement of when to prefer this tool over dashy_sections or dashy_config. The dry-run/write gating hints at a safe workflow but is not framed as when-to-use guidance.

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