Skip to main content
Glama
Sign In
togaf10_EAP_MCP

togaf10_EAP_MCP

by Waganawa-Megumin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open the live dashboard in a browser

open_dashboard

Launch a local HTTP server and open a live dashboard in your browser, returning the URL. The dashboard updates automatically over SSE for current status and includes print-ready CSS.

Instructions

ローカル HTTP サーバー(127.0.0.1)を起動し、ブラウザでライブダッシュボードを開いて URL を返す。SSE で状態変更を検知して自動更新、印刷用 CSS 付き。 / Start a local HTTP server on 127.0.0.1, open the live dashboard in a browser, and return the URL. It live-updates over SSE and carries print CSS.

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
langNo出力言語 / Output languageboth
openNoブラウザを自動で開く / Launch the browser automatically

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full transparency burden. It goes beyond a generic 'open dashboard' statement by disclosing that it starts a local HTTP server, live-updates over SSE, and includes print CSS. It does not cover server lifecycle or response structure, but the core behavior is well exposed.

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?

The description is concise and front-loaded with the main action, then adds useful behavioral details (SSE, print CSS). The bilingual duplication is necessary for the audience and every sentence contributes information without fluff.

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

Completeness3/5

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

Given no annotations and no output schema, the description is the main source of context. It explains the core behavior and says a URL is returned, but it does not specify the response format or clarify behavior when open=false, such as whether the server still starts. These are minor gaps for a simple tool but prevent a higher score.

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?

The schema covers 100% of parameters with type, enum, default, and descriptions, so the baseline is 3. The tool description adds little parameter-specific meaning beyond implying that 'open' relates to launching a browser; the schema already handles the details.

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 clearly states the tool starts a local HTTP server on 127.0.0.1, opens the live dashboard in a browser, and returns the URL. This is a specific verb+resource action that differentiates it from sibling 'get_dashboard', though it does not explicitly name that alternative.

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 usage context is implied: use when the user wants the live dashboard opened in a browser. However, there is no explicit guidance on when to use this tool versus alternatives like get_dashboard or open_start, and no exclusions or prerequisites are given.

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