Skip to main content
Glama
Sign In
MCP SteamOS Devkit

MCP SteamOS Devkit

by elliotttate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sync_devkit_utils

Syncs Valve's devkit-utils helper scripts to the target device, enabling SteamOS development and diagnostics.

Instructions

Sync Valve's devkit-utils helper scripts to ~/devkit-utils on the device.

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

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

B3/5.0
Behavior2/5

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

The description lacks details on behavioral traits such as whether existing files are overwritten, required permissions, or if the operation is destructive. With no annotations, the description carries the burden but fails to disclose side effects or safety considerations.

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 12 words, extremely concise. However, it sacrifices necessary detail for brevity, making it less informative than it could be while still being efficient.

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?

Despite the presence of an output schema, the description does not mention return values or behavior. With four parameters and no parameter documentation, the description is incomplete for a sync tool, failing to specify what 'target' refers to or how the sync occurs.

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?

The input schema has 0% description coverage, meaning no parameter descriptions exist. The tool description does not explain any of the four parameters (login, target, http_port, name_type), leaving the agent without guidance on their meaning or usage.

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 the action (Sync) and the specific resource (Valve's devkit-utils helper scripts to ~/devkit-utils on the device). It distinguishes from sibling tools like sync_logs and sync_tracking_dataset by specifying the exact scripts and destination.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives, such as when the devkit-utils need updating. The usage is implied (to sync helper scripts), but no exclusions or context for when to avoid it are provided.

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