Skip to main content
Glama
Sign In

TikTikLuck

by com.tiktikluck
OverviewDiscussionsAdmin

Invent a new game

invent_game

The AI invents a new kind of game from your description — luck or skill, solo or (multiplayer=true) a luck game for live rooms of up to 20 — writes its code and tests it. Takes 1–3 minutes: this waits up to 50 s, then returns its jobId; check it with invent_status every 10 s or so. Then publish_invented_game. In a luck template, outcomes[].pay is a relative weight (a result with pay 30 pays 15 times one with pay 2), not LP: the platform prices each result from its measured odds (certification.outcomes[].multiplierX100 in invent_status).

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

Input Schema

NameRequiredDescriptionDefault
aiNoours (default) | own: build with your person's own AI key, on the model they picked in Profile (they pay for it; no hourly limit)
baseNoTo change an invented game instead: its template (from invent_status)
baseIdNoOr, to change a published invented game: its id (from list_games / get_invented_game). Its template is fetched for you, with its pay weights
changeNoWith base or baseId: the change, 3..800 chars
descriptionNoThe game, 10..2000 chars
multiplayerNoA multiplayer luck game for live rooms

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ai
      Added value: +{
+  "description": "ours (default) | own: build with your person's own AI key, on the model they picked in Profile (they pay for it; no hourly limit)",
+  "enum": [
+    "ours",
+    "own"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the safety profile (not read-only, not destructive, not idempotent), and the description adds substantial context beyond that: multi-minute latency, a synchronous wait capped at 50 s followed by an async jobId, the polling cadence, and the non-obvious pricing semantics of outcomes[].pay as a relative weight rather than LP. This is exactly the behavioral disclosure an agent needs before committing to a slow, non-idempotent call.

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?

Purpose is front-loaded and every sentence carries information, including the follow-up tools. The second clause ('luck or skill, solo or (multiplayer=true) a luck game for live rooms of up to 20') is cramped and the final pay-weight sentence is dense, but nothing is wasted.

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

Completeness5/5

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

For a 6-parameter, zero-required, async tool with no output schema, the description covers the missing pieces: it names the return value (jobId), the polling tool, the downstream publish step, and the timing envelope. An agent could call this correctly without inspecting any other tool.

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%, so the baseline is 3, but the description adds real meaning beyond the schema: multiplayer=true constrains the result to a luck game for live rooms of up to 20, and it explains how pay weights are converted to multipliers by the platform. The ai and base/baseId semantics are left entirely to the schema.

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?

States a specific verb and resource: the AI invents a new game from a description, writes its code and tests it, plus a variant mode (change an existing invented game via base/baseId). It does not distinguish itself from likely-overlapping siblings such as design_skill_game or design_luck_board, which is the only thing keeping it from 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 Guidelines4/5

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

Provides an explicit workflow: call this, poll invent_status every ~10 s, then publish_invented_game, and states the 1–3 minute / 50 s wait budget. It also explains the change-an-existing-game path. It stops short of saying when a caller should prefer design_skill_game or design_luck_board instead.

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

All TikTikLuck toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources