MCP SteamOS Devkit

by elliotttate

Overview Schema Source Related Servers Discussions Admin

Python

Local

sync_logs

Sync Steam, SteamVR, and system dumps from a devkit device to a local folder for diagnostics.

Instructions

Sync Steam logs, SteamVR logs, and /tmp/dumps to a local folder.

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>",
      "local_folder": "<local_folder>"
    },
    "name": "sync_logs"
  }
}

Input Schema

Name	Required	Default
`login`	No
`target`	Yes
`http_port`	No
`name_type`	No	guess
`device_name`	No
`local_folder`	Yes
`steamvr_logpath`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. 'Sync' is ambiguous—could mean copy or move—and there is no mention of side effects, permissions, or network requirements. Minimal transparency.

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 description is a single sentence with no wasted words. However, it could be slightly longer to include essential parameter context without becoming verbose.

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

Completeness1/5

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

Despite an output schema existing, the description lacks crucial details about 7 parameters, no annotations, and no explanation of the sync behavior. Extremely incomplete for a tool of this complexity.

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?

With 0% schema description coverage, the description should compensate for parameter details. It only describes the overall action, ignoring all 7 parameters (target, local_folder, etc.). Fails to add meaning beyond the schema.

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 clearly states the action (sync), resources (Steam logs, SteamVR logs, /tmp/dumps), and destination (local folder). However, it does not differentiate from sibling tools like sync_devkit_utils, which also sync logs, lacking specificity.

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 guidance on when to use this tool versus alternatives such as steam_logs_manifest or sync_tracking_dataset. The description does not provide context prerequisites or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server