Skip to main content
Glama
Sign In
MCP SteamOS Devkit

MCP SteamOS Devkit

by elliotttate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_titles

Retrieve a list of devkit titles installed on a SteamOS Devkit device, using the target address and optional authentication.

Instructions

List devkit titles installed under ~/devkit-game.

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": {
      "target": "<target>"
    },
    "name": "list_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault
loginNo
targetYes
http_portNo
name_typeNoguess

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Without annotations, the description only says 'List', implying a read operation, but does not disclose any potential side effects, permissions needed, or behavior beyond a basic listing. The output schema exists but is not referenced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but insufficiently informative given the tool's complexity. It could include more context without becoming verbose.

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?

With 4 parameters (1 required) and no parameter descriptions, the description is incomplete. It doesn't summarize the output (though schema exists) or mention prerequisites like having devkit-game set up. Sibling tools suggest a workflow, but the description lacks integration context.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any of the 4 parameters (login, target, http_port, name_type). The purpose 'list titles' does not clarify what 'target' or 'http_port' mean.

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?

The description clearly states 'List devkit titles installed under ~/devkit-game', which is a specific verb and resource, and differentiates from siblings like delete_title, upload_title, and run_title.

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?

No guidelines on when to use this tool versus alternatives. The description does not provide context for typical usage scenarios or state when not to use it.

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