Skip to main content
Glama

Open the dashboard

open_dashboard

Starts the visual Life Compass dashboard on your computer and returns a private link to open it in a browser, showing rings, mountain, habits, goals, and wins from your local plan.

Instructions

Starts the visual Life Compass dashboard on this computer (rings, mountain, habits, goals, wins) and returns a private link to open in a browser. It reads the same local plan file and stays up while this app is open.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it says the dashboard starts on this computer, returns a private link, reads the same local plan file, and stays up while the app is open. It does not describe failure modes, ports, or whether repeated calls create multiple instances.

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?

Two tightly written sentences front-load the core action and then add the relevant local/private/lifetime context. No sentence is wasted.

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 zero-parameter local dashboard launcher with no output schema, the description gives enough context about what it starts, what it returns, and how long it stays available. The remaining operational details are minor for correct invocation.

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?

This tool has zero parameters, so there is no parameter meaning to add beyond the schema. The baseline for a parameterless tool is appropriate here.

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

Purpose5/5

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

The description uses a specific verb and resource: starts the visual Life Compass dashboard and returns a private link to open in a browser. It also lists dashboard contents, making clear this is a visual UI launcher rather than one of the sibling plan-data tools.

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 implies usage for viewing the visual dashboard, but it does not explicitly say when to use this instead of the many get/save/review sibling tools. No exclusions or alternatives are named.

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