Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save Look settings

save_look
Destructive

PARTIAL SAVE: writes ONLY the 'Look' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Look - the look of the app's interface laid over the project's src/ui.config.ts at start, no rebuild: Theme (UI kit colour tokens -> #rrggbb: bgTop, bgBottom, panel, panelDeep, panelEdge, ink, nav, text, textDim, gold, goldDeep, green, greenDeep, blue, blueDeep, red, redDeep, purple, purpleDeep, orange, orangeDeep, teal, tealDeep; derived tones are computed), Radius and ButtonRadius (px 0..64), Outline (px 0..8), Background (a screen pattern id: gear (the default game-gear pattern), plain, dots, stripes, grid, hex, stars, waves, checker, confetti, bubbles, zigzag, diamonds, clouds, leaves, circuit, sparkles, rays, bricks, paws, snow), MotionSpeed (0.1..5, 1 default), MotionIntensity (0..3, 1 default), Particles, SoundSet (classic, soft, retro, magic, sci-fi, wood). Every field optional; unset keeps the project's own value.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title_id": "<title_id>",
      "value": "<value>"
    },
    "name": "save_look"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesThe look of the app's interface over the project's src/ui.config.ts, without a rebuild: colours, corners, outline, a screen pattern, animations and interface sounds. Every field is optional; what is not set keeps the project's own value.
title_idYesTitleID, для которого сохраняются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description usefully narrows that by explaining the write is partial and non-rebuilding, and that unset fields are preserved. It does not say whether changes take effect immediately for live players, whether the previous look is recoverable, or what permissions/title ownership are required — notable gaps for a tool flagged destructive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical scoping statement is correctly front-loaded, but the body re-enumerates all twenty-two theme colour tokens and twenty-one background patterns that already appear verbatim in the schema, making a single dense run-on paragraph where a short scope statement plus a pointer to the schema would suffice.

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?

For a two-parameter mutation with a nested object and no output schema, the description covers what changes, what is preserved, defaults, and validation ranges — enough to call it correctly. Missing only the outcome/permission details that would make it fully self-sufficient.

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: it lists valid ranges (Radius 0..64, Outline 0..8, MotionSpeed 0.1..5, MotionIntensity 0..3) alongside defaults and explains that derived theme tones are computed rather than supplied. It also names 'gear' as the default background pattern, which the schema's Background description omits.

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 opening sentence names a specific operation and its exact scope: "writes ONLY the 'Look' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched." That scope statement alone distinguishes it from the many sibling save_* tools that write other sections of title data.

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?

The description gives a clear usage context — use this to change the interface look without a rebuild — and states the key calling convention: "Every field optional; unset keeps the project's own value." It does not explicitly rule out alternatives (e.g., save_title_data or a full config save) or mention reading current values via get_look first, so it stops short of full when/when-not guidance.

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

All iDos Games 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