Skip to main content
Glama
Sign In
Sailfish Devel MCP

Sailfish Devel MCP

by abranson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

User Bus Call

sailfish_device_user_bus_call

Run typed dbus-send method calls on a Sailfish OS device's defaultuser session bus. Use it to invoke D-Bus methods for app or service debugging.

Instructions

Run a typed dbus-send method call on the defaultuser session bus.

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": {
      "destination": "<destination>",
      "path": "<path>",
      "interface": "<interface>",
      "member": "<member>"
    },
    "name": "sailfish_device_user_bus_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
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.
memberYes
timeoutNoCommand timeout in seconds.
argumentsNoRaw dbus-send argument strings, for example string:/tmp/file.
interfaceYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is largely covered structurally. The description adds little beyond that — it names the 'defaultuser session bus' scope but says nothing about mutation risk, required permissions, side effects, or response behavior for a tool that can invoke arbitrary dbus methods.

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?

A single efficient sentence with no filler, and the core action is front-loaded. It is concise to the point of under-specification, but it wastes no words.

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

Completeness2/5

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

For a 7-parameter, no-output-schema tool that can invoke arbitrary dbus methods on a session bus, the description is far too thin. It omits parameter meaning, usage conditions, and any behavioral/return context, leaving substantial gaps unfilled by schema or annotations.

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 only 43% across 7 parameters, and the description contributes no parameter meaning at all. It never explains destination, path, interface, member, or arguments, leaving the required dbus-send addressing fields undocumented outside the schema while the coverage gap remains.

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 gives a specific verb ('Run') and resource ('typed dbus-send method call on the defaultuser session bus'), which is more than a tautology. However, it does not distinguish this tool from the adjacent sibling sailfish_device_user_session_command, leaving the agent to guess which session-level tool to use.

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 when-to-use guidance, no when-not-to-use, and no named alternative. The description merely states what the tool does, not the situation that should select it over sailfish_device_user_session_command or sailfish_device_command_start.

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