Skip to main content
Glama
Sign In
Sailfish Devel MCP

Sailfish Devel MCP

by abranson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

User Session Command

sailfish_device_user_session_command

Run a short command in a device's Sailfish user-session D-Bus environment, capped at 15 seconds; use the async start tool for longer jobs.

Instructions

Run a short command, limited to 15 seconds, with the configured Sailfish user-session D-Bus environment. Use sailfish_device_command_start for anything that may run longer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "sailfish_device_user_session_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoConfigured device alias or ssh target. When the user says the device is attached over USB, use 'usb' for the default device or 'usb:<name>' when the user supplies a device name. The USB connection trusts that name for device metadata and does not resolve it through DNS.
commandYesCommand argv to run; shell parsing is not applied.
timeoutNoCommand timeout in seconds; long commands must use an async job.
verboseNoInclude full command, stdout, and stderr details for diagnostics.
run_as_userNoRun through runuser/su as the configured device username.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-readonly, open-world, non-idempotent, and non-destructive behavior. The description adds meaningful execution context beyond annotations by specifying the 15-second limit and the configured user-session D-Bus environment, though it does not discuss permissions or return behavior.

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 sentences with no wasted wording. The key constraint and the alternative tool are both front-loaded.

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?

For a command-execution tool with full schema coverage and annotations covering safety, the description is nearly complete for selection and invocation. It does not describe result/output behavior, which leaves a minor gap because there is no output schema.

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 description coverage is 100%, so the parameter semantics are already well documented in the schema. The description does not add parameter-level syntax or format details beyond what the schema provides, so the 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?

States a specific verb and resource: run a short command in the configured Sailfish user-session D-Bus environment. It also distinguishes itself from sailfish_device_command_start, so an agent can tell them apart without opening both schemas.

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

Usage Guidelines5/5

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

Explicitly gives the alternative for longer-running commands: use sailfish_device_command_start for anything that may run longer. The short-command scope is front-loaded, making the when-to-use boundary clear.

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