Skip to main content
Glama
Sign In
Starmux

Starmux

by cookyecat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_config

Read-only

Retrieve complete server configuration as JSON to inspect blocked commands, allowed directories, file limits, telemetry, current client, and system details for access control or troubleshooting.

Instructions

                    Get the complete server configuration as JSON. Config includes fields for:
                    - blockedCommands (array of blocked shell commands)
                    - defaultShell (shell to use for commands)
                    - allowedDirectories (paths the server can access)
                    - fileReadLineLimit (max lines for read_file, default 1000)
                    - fileWriteLineLimit (max lines per write_file call, default 50)
                    - telemetryEnabled (boolean for telemetry opt-in/out)
                    - currentClient (information about the currently connected MCP client)
                    - clientHistory (history of all clients that have connected)
                    - version (version of the DesktopCommander)
                    - systemInfo (operating system and environment details)
                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

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

Input Schema

NameRequiredDescriptionDefault
originNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds that the payload includes clientHistory, systemInfo, and allowedDirectories, hinting at potentially sensitive content, but says nothing about permissions, redaction, or side effects beyond that. With annotations carrying the safety burden, this is adequate but not rich.

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 main statement is front-loaded and the bulleted field list is an efficient way to enumerate a return shape that has no output schema. The closing sentence about 'DC: ...' / 'use Desktop Commander to ...' is orientation fluff that does not help an agent invoke this tool.

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?

With no output schema, the enumerated config fields are the only documentation of the return value, and they cover all ten fields plus two defaults (1000 and 50), which is genuinely useful. The gaps are the undocumented `origin` parameter and no note on how often config changes or whether the read is cached.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the single `origin` parameter or its `ui`/`llm` enum. The schema must carry that burden entirely, and while the enum values are fairly self-explanatory, the description does nothing to explain what difference the origin makes.

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 opens with a specific verb and resource ('Get the complete server configuration as JSON') and enumerates exactly what the configuration contains, so an agent knows precisely what this returns. It never differentiates itself from the obvious sibling set_config_value, whose job is the inverse (writing config), so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus alternatives such as get_usage_stats or get_recent_tool_calls, and no mention of set_config_value as the mutating counterpart. The trailing note about 'DC: ...' phrasing is about how to reference Desktop Commander in instructions, not about when this tool is appropriate.

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