Skip to main content
Glama
Sign In
Stellaris MCP

Stellaris MCP

by GDM-Pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

usage_dashboard

Launch a local web dashboard to view Claude Code token usage with interactive charts in VS Code Simple Browser. No API key required.

Instructions

Launch a local web dashboard showing Claude Code token usage with interactive charts. Opens in VS Code Simple Browser. No API key required.

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": "usage_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNoPort for the local HTTP server (default: 8090)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.4.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that it launches a local web server, opens in VS Code Simple Browser, and requires no API key. Lacks details on port collision handling or cleanup, but sufficient for a non-destructive launch tool.

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?

Single sentence of 20 words, front-loads the main purpose, and every phrase adds value. No unnecessary information.

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?

No output schema exists, but the description explains the user-facing result (interactive charts and dashboard). For a launch action, this is adequately complete; missing details about the server shutdown or refresh behavior would improve but not essential.

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%—the single 'port' parameter is already described in the schema. The description adds no additional context beyond what is in the schema, so baseline 3 is appropriate.

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?

Clearly states verb 'Launch' and resource 'local web dashboard showing Claude Code token usage with interactive charts'. Distinguishes from sibling tools like usage_stats or usage_breakdown which are non-interactive data reports.

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?

Explicitly indicates when to use (to view token usage interactively) and notes 'Opens in VS Code Simple Browser' and 'No API key required'. However, it does not mention when not to use or compare with sibling usage tools.

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

Deploy Server

Other Tools