Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
open_appA

启动一个已安装的应用。

Args: name: 应用显示名(如 "Docker Desktop")或 exe 名(如 "notepad")。 会按注册表 DisplayName 或 PATH 查找。 path: 应用 exe 的完整路径(优先于 name 使用)。

Returns: 是否成功启动,以及使用的路径/对象。

open_urlA

用浏览器打开一个 URL。

Args: url: 完整地址(如 http://localhost)。 browser: default | chrome | edge | firefox。

Returns: 是否成功发起打开。

screenshotA

截取全屏 PNG。

Args: path: 保存路径;省略则存到临时目录。

Returns: 保存的文件路径。

get_screen_sizeA

返回虚拟桌面尺寸(物理像素)。

app_runningA

检查进程是否在运行。

Args: name: 进程名(如 "Docker Desktop"、 "docker"、 "com.docker.backend")。

Returns: running: 是否在运行;pids: 匹配到的进程 ID(可能多个)。

waitA

等待 ms 毫秒(用于给服务启动/界面刷新留时间)。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct action: launching an app, opening a URL, capturing the screen, getting screen dimensions, checking a process, and waiting. There is no meaningful overlap or ambiguity among them.

Naming Consistency3/5

The naming is generally readable and mostly uses snake_case, but conventions vary: open_app/open_url/get_screen_size follow verb_noun, while app_running and screenshot break that pattern, and wait is just a bare verb. This is a minor inconsistency rather than chaos.

Tool Count5/5

Six tools is a reasonable, well-scoped set for a small desktop action utility. Every tool serves a practical purpose and the count feels neither bloated nor thin.

Completeness4/5

The set covers the core lifecycle of opening apps/URLs, checking whether they started, waiting, and capturing screen state. Minor gaps exist such as no close_app or window interaction, but agents can still complete common workflows without major dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues