Skip to main content
Glama

List Kaigen templates

list_templates
Read-onlyIdempotent

The templates a new Kaigen game or 3D app can start from (kaigen projects new --template <name>), each with its description.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds that each template comes with its description and how the returned names are consumed by the CLI, which is modest but real added context; ordering, count, or formatting of the listing remains undisclosed.

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?

One short sentence that front-loads the resource and appends the CLI consumption hint; nothing is wasted. The phrasing is slightly convoluted — 'The templates a new Kaigen game ... can start from' — but it remains readable in a single pass.

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 parameters, rich annotations, and no output schema, this is a nearly self-describing tool, and the description still adds what each item includes and how names are used. Only minor gaps remain, such as whether all templates are returned or how they are ordered.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The parenthetical command reference helpfully shows where the returned values go, without adding conflicting semantics.

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 identifies the resource precisely — templates a new Kaigen game or 3D app can start from — and states that each entry carries a description, which tells an agent what the result set contains. The verb 'list' is only implied by the name/title rather than stated in the description, and there is no explicit contrast with siblings like get_started or search_docs, keeping it below 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?

The parenthetical `kaigen projects new --template <name>` implicitly tells the agent that these names feed project scaffolding, so the usage context is inferable. However, it never says when to call this instead of get_started or search_docs, and no prerequisites or exclusions are given.

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.