Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Save Platform Bridge settings

save_platform_bridge
Destructive

PARTIAL SAVE: writes ONLY the 'PlatformBridge' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Platform bridge - what the game takes from the player's idosgames.com account and what it lets players show on their public profile. Profile: Off / Default (unset: the platform name and avatar until the player renames themselves in the game) / Always (every platform login overwrites them). Friends: TitleOnly (unset) / TitleAndPlatform (plus mutual follows on idosgames.com whose both sides play this game) / PlatformOnly (only those; in-game friend requests are refused) - applies to EVERY friends-based system: friends list and leaderboard, gifts, attack targets, friends-only Workshop items, recommendations. Notifications: which in-game notifications (Attack, Raid, FriendAdded, WorkshopSale) also reach the idosgames.com notification bell; empty = none. Guests never get platform data; the economy never crosses the bridge; turning the bridge off deletes nothing.

Input Schema

NameRequiredDescriptionDefault
valueYesPlatform bridge: what the game takes from the player's idosgames.com account and what it lets the player show on their public profile. Everything is off by default except the profile. What the PLAYER shares about themselves on the platform (the Played and Workshop tabs of their profile) is not the publisher's decision and is not configured here. Guests (no platform account) never get platform data. The economy never crosses the bridge.
title_idYesTitleID, для которого сохраняются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / value / properties / Recording
      Added value: +{
+  "description": "Lets players record videos of the game on idosgames.com (the Clip and Record buttons, background recording of the last minute, Best moments). Unset = on; false = no recording buttons and no background recording. Recording happens in the player's browser; nothing is uploaded.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
  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 say readOnlyHint=false and destructiveHint=true; the description goes well beyond by disclosing unset-value defaults ('Default'/'TitleOnly'), scope of blast radius ('applies to EVERY friends-based system'), side-effect guarantees ('turning the bridge off deletes nothing', 'guests never get platform data', 'the economy never crosses the bridge'), and that recording stays in-browser with nothing uploaded.

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 mechanical fact (partial save) is admirably front-loaded, but the bulk of the passage re-enumerates the Profile/Friends mode semantics that the schema already defines verbatim, making it denser and more redundant than necessary.

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 nested-object mutation tool with no output schema, the definition covers defaults, per-field behavior, downstream effects on game systems, and what is explicitly not affected, leaving an agent with everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and every nested property (Profile, Friends, Recording, Notifications) is already documented in the schema, so the schema carries the burden. The description largely restates the same enum semantics rather than adding new format or syntax guidance, matching the baseline 3.

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 line states a specific verb, resource, and scope: 'PARTIAL SAVE: writes ONLY the PlatformBridge field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched.' This lets an agent distinguish it from the many generic save_* siblings that write whole config sections.

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 'PARTIAL SAVE' framing clearly establishes the context in which this tool should be used (changing only bridge settings without touching other v1/v2 fields), but it never explicitly names an alternative tool or a when-not-to-use condition, so routing still requires inference.

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