Skip to main content
Glama

Get started with Kaigen

get_started
Read-onlyIdempotent

The exact commands to install the Kaigen CLI, sign in, install the engine, create a game from a template, run it and publish it to a playable link, for Windows, macOS or Linux, and how to add the Kaigen skill to a coding agent.

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

Input Schema

NameRequiredDescriptionDefault
osNoThe user's operating system

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine scope detail (which steps the returned commands cover, and cross-platform support), but says nothing about the response format, whether commands are versioned, or any caveats about executing them.

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?

A single dense sentence that front-loads the payload (exact commands) and enumerates the covered steps in execution order. It is slightly run-on and could be split, but every clause carries information about the covered scope.

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

Completeness4/5

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

With zero required parameters, one optional enum, no output schema, and a closed-world read annotation, this is close to complete: the agent knows what the tool returns and which OS values exist. The only gap is that it doesn't state the return shape (e.g., markdown code blocks) for a tool whose whole product is textual commands.

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

Parameters4/5

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

Schema coverage is 100% with an enums-constrained os field that is self-describing, so the baseline is already 3. The description adds value by framing the platform dimension ("for Windows, macOS or Linux"), making clear the returned commands are platform-tailored rather than generic.

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 names a concrete deliverable: "the exact commands to install the Kaigen CLI, sign in, install the engine, create a game from a template, run it and publish it." That is a specific resource (onboarding command sequence) rather than a vague restatement of the title. It does not explicitly contrast itself with about_kaigen or search_docs, so it falls short of a 5.

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?

Usage is only implied: an agent can infer this is the first-run onboarding path because it enumerates install-through-publish steps. There is no explicit statement of when to call this versus about_kaigen or search_docs, and no exclusions or prerequisites called out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.