Skip to main content
Glama
Sign In
Sailfish Devel MCP

Sailfish Devel MCP

by abranson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Sailfish Devices

sailfish_devices
Read-onlyIdempotent

List configured Sailfish OS device aliases and SSH targets so you can select a device and connect for development tasks.

Instructions

List configured Sailfish OS device aliases and SSH targets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds only the scoping detail that results are drawn from configured aliases and SSH targets — modest extra context about what 'device' means here, but no disclosure of ordering, environment sources, or failure behavior when nothing is configured.

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?

A single front-loaded sentence with no filler, hedging, or redundant restatement of the title. Every word contributes scope information.

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 zero-parameter, read-only listing tool with rich annotations and no output schema, this is nearly complete; the only gap is that nothing tells the agent how devices are enumerated or what happens when the configuration is empty. That gap is small given the tool's simplicity.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4: there is nothing for the description to disambiguate. It correctly stays silent rather than inventing parameter behavior.

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?

States a specific verb (List) and a specific resource (configured Sailfish OS device aliases and SSH targets), which is more precise than the generic 'devices'. It reads as a discovery/read tool distinct from the many sailfish_device_* action tools, though it never names a sibling to sharpen the boundary (e.g. vs. sailfish_device_setup, which likely also touches device configuration).

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, nor any prerequisite such as needing devices to be configured first. An agent can infer it is a discovery step before the device_* tools, but the description does not say so explicitly.

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