Skip to main content
Glama
Sign In
MCP SteamOS Devkit

MCP SteamOS Devkit

by elliotttate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

steam_frame_replay_script_template

Returns JSON templates for launch, ADB, CEF UI, tracking capture, and pose replay scripts to streamline SteamOS Devkit device scripting.

Instructions

Return JSON templates for launch, ADB, CEF UI, tracking capture, and future pose replay scripts.

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

Input Schema

NameRequiredDescriptionDefault
kindNofull

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the core function. It does not state whether the operation is purely read-only, if authentication is required, or if there are side effects. This leaves the agent guessing about safe usage.

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 that front-loads the main purpose. It is concise and contains no unnecessary words. However, it could be slightly improved by including brevity and good structure.

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

Completeness3/5

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

The description gives the overall purpose but lacks details about parameters and usage context. An output schema exists, so return values are likely covered there. For a simple tool, the description is minimally adequate but has clear gaps.

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 one parameter 'kind' with default 'full', but the description does not mention it or explain its meaning. With 0% schema description coverage and no parameter documentation in the description, the agent has no understanding of how to use the parameter.

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 tool returns JSON templates for specific script types (launch, ADB, CEF UI, tracking capture, future pose replay). It uses a specific verb 'Return' and identifies the resource 'templates'. The tool's purpose is distinct from sibling tools like steam_frame_cef_pages or steam_frame_automation_plan, which focus on different aspects.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, scenarios, or excluded use cases. Given the large number of sibling tools, explicit usage context would be beneficial.

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