Skip to main content
Glama
Sign In
LorAI MCP

LorAI MCP

by hongyue0721
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

start_game

Clicks Continue on the title screen and waits for the main UI, retrying until the scene transitions away from Title.

Instructions

Click Continue on the title screen and wait for the main UI.

The HTTP bridge may go down during scene transition; this tool retries until the scene is no longer Title.

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

Input Schema

NameRequiredDescriptionDefault
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior5/5

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

The description discloses that the HTTP bridge may go down during scene transition and that the tool retries until the scene is no longer Title. Without annotations, this is crucial behavioral context.

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?

The description is two concise sentences with no fluff. Front-loaded with the primary action, followed by essential retry behavior.

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?

While the core purpose and retry mechanism are covered, missing parameter documentation and lack of differentiation from siblings leave gaps. The output schema exists, so return values are not required.

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?

Schema description coverage is 0%, and the description does not mention the 'wait_seconds' parameter at all, leaving its purpose and effect undocumented. The description fails to compensate for the schema gap.

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 clicks 'Continue' on the title screen and waits for the main UI, specifying the exact action and resource. It distinguishes from siblings like 'skip_story' which handles story scenes.

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 description implies usage when the game is at the title screen, but does not explicitly state when to use this tool vs alternatives. No exclusions or when-not-to-use guidance is 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