Skip to main content
Glama

setup

Install the toolchain: Source 2 Viewer CLI, CSDK 13 and the compiler's Wine prefix. Downloads run in the background, so call again to see progress; a step it can't do itself says what the user has to do.

Instructions

Install the toolchain: Source 2 Viewer CLI, CSDK 13 and the compiler's Wine prefix. Downloads run in the background, so call again to see progress; a step it can't do itself says what the user has to do.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose meaningful traits beyond the schema: the operation is asynchronous ('downloads run in the background'), progress is observed by re-invoking, and some steps surface manual instructions for the user. However, it does not state whether re-running is idempotent versus triggering a fresh install, whether network access or elevated permissions are required, or what side effects the Wine prefix setup has. Those are notable gaps for an installer with zero annotation coverage.

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?

Two sentences, front-loaded with what gets installed before the async/progress caveat. Nothing is repeated from structured fields and no sentence is filler.

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 output schema exists, so return values need not be explained, and the async polling behavior is covered. Still, for an installer that must precede compile_source and launch_game, the description never states prerequisites, ordering relative to siblings, or idempotency, which leaves gaps an agent would need to infer.

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

Parameters3/5

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

There are zero parameters, so there is no parameter semantics to add and the schema imposes no ambiguity. The baseline for a parameterless tool is appropriate here; the description adds no parameter-level meaning because none exists.

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 opens with a specific verb and resource ('Install the toolchain') and enumerates the three components installed: Source 2 Viewer CLI, CSDK 13, and the compiler's Wine prefix. That is concrete enough to separate it from siblings like compile_source or bridge_install, though it does not explicitly name which sibling handles a related-but-different install task.

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

Usage Guidelines4/5

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

It gives clear operational context: downloads run in the background, so the agent should call again to observe progress rather than assume completion. It also sets the expectation that steps outside the tool's control will report what the user must do. It stops short of naming an alternative tool or stating when not to use this one.

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