Skip to main content
Glama

dashy_system

Read-only

Check Dashy process health, capture host resource info, and retrieve the config JSON Schema through read-only health, info, and schema actions.

Instructions

Dashy process health, host resource snapshot, and the config JSON Schema. Reads only. Actions: health (GET /healthz), info (GET /system-info), schema (GET /schema.json). Dashy has no rebuild endpoint in 4.9.19.

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

Input Schema

NameRequiredDescriptionDefault
actionYesDashy operation to call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by tying each action to a concrete HTTP endpoint and flagging a version-specific capability gap (no rebuild endpoint in 4.9.19). It does not describe the shape of the returned payload, but no output schema exists to fall back on.

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?

Three short sentences, front-loaded with the resource summary, then the read-only constraint, then the action-to-endpoint mapping and caveat. No wording is redundant with the schema beyond what is needed for orientation.

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

Completeness5/5

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

For a single-enum read-only diagnostic tool with full schema coverage and complete annotations, the description covers all three actions, their underlying endpoints, the read-only nature, and a version caveat that would otherwise cause a failed attempt. Nothing an agent needs in order to call it correctly is missing.

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?

With only one required parameter at 100% schema coverage, the schema already carries the baseline. The description nevertheless adds meaning by explaining what each enum value actually retrieves (health → /healthz, info → /system-info, schema → /schema.json), which is more than the schema's generic "Dashy operation to call."

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 names three concrete resources (process health, host resource snapshot, config JSON Schema) and maps each to a specific action/endpoint pair, so the agent knows exactly what the tool retrieves. It does not explicitly contrast itself with the sibling tools dashy_config/dashy_items/dashy_keys/dashy_sections, though the system-level scope makes the distinction inferable.

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?

"Reads only" plus the closing note "Dashy has no rebuild endpoint in 4.9.19" give clear context and a useful when-not boundary that prevents a wasted call. There is no explicit statement of when to prefer this over the sibling config/item tools, so it stops short of full routing guidance.

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